Wallets, inboxes, browsers, sandboxes, memory, and identity, all provisioned in a single install.
Your agent shouldn't either.
Today, shipping an agent means stitching together a different provider for each of those things, every one with its own auth flow, error model, and monthly invoice, plus whatever glue code you end up writing yourself to make the pieces talk to each other. That's what we're collapsing into one import.
Because every interface is normalized, you can swap the provider behind any one of them with a config change, or have the SDK fall back automatically when one goes dark, all without touching your application code.
More on the way.
A single call provisions your agent with an inbox, a spending-capped card, and a cloud browser, leaving you free to focus on what it should actually do.
import { Inlet } from "inlet"; const inlet = new Inlet({ apiKey: process.env.INLET_API_KEY }); // one call provisions an inbox, a card, and a cloud browser. const agent = await inlet.agents.create({ name: "procurement", email: { domain: "yourco.ai" }, wallet: { monthlyLimit: 2000 }, }); // on an inbound purchase request: find it, buy it, reply with the receipt. agent.email.on("message", async (msg) => { const session = await agent.browser.start(); await session.act(`find and buy: ${msg.body}`); await agent.email.reply(msg, "done — receipt attached."); });
Add yourself to the list and we'll reach out as space opens up.