Custom agentic AI — questions before you start

What a custom agentic AI is at x402.press, what it costs, and what it can do. Written as answers rather than marketing: where something is not built yet, the answer says so.

What is a custom agentic AI?

An AI agent assembled for one organisation's work: it has the tools that work needs, the data sources it may read, a wallet that pays for what it uses, and limits on what it may spend. It is not a chat window you subscribe to — it is a workspace that belongs to you and does a job.

How is this different from an AI subscription?

A subscription sells you access to a model. Here you get an agent built from parts, and it pays per call for what it actually uses — current news, a reasoning model, a document engine — from your own wallet. Nothing is marked up inside a subscription, and you can see every call it paid for.

What does it cost to start?

Five dollars, paid in USDC on Base over the x402 protocol. That five dollars is not a fee: it becomes the workspace's opening credit — it is your first top-up, and your agent spends it on what it buys. You top up again when it runs out, and there are no monthly charges in between.

Who pays for what the agent buys?

You do, from your own wallet, per call, under the ceilings you set — a maximum number of paid calls per message, a maximum per message, and a maximum per day. The agent never holds signing authority over your funds: it asks for each payment, and the workspace keeps a record of every call it paid for.

Can it use our own email, files and drives?

That is what connections are for, and they are always your accounts: your mailbox, your drive, your chat. Telegram is built today; email is the next one being built, and it is what four of the five roles in the bin are waiting on. The workspace refuses anything that has not been explicitly connected and allow-listed.

What kinds of agents can be assembled today?

The bin holds five roles: a researcher, a purchase manager, a sales agent, a customer service agent and a personal assistant. One of them — the researcher — can be assembled today. The other four are each waiting on a single part (inbound email), not on a rebuild.

Where does our data live?

In your own workspace, in its own container, with its own volume. It is separate from every other client's. Credentials for your connections are held only inside that container, readable only by it, and never written into logs or handed to anything outside it.

How does a build actually go?

You sign in and describe the agent you want. We spend a short conversation — about five exchanges — turning that into a concrete proposal: the role, the parts, the connections, the limits and the projected running cost. It is approved by a person here, you pay the five dollars, and the workspace is provisioned. After that it is yours, and changes come back through the same conversation.

What stops the agent from doing something expensive or irreversible?

Two things, both enforced rather than promised. Every paid call is checked against the ceilings before it is made, and anything that sends, publishes or spends outside those limits escalates to you instead of proceeding. Its spend is recorded per message and per day, so you can always see what it did and what it cost.

What can be built, today

The bin's own account of itself lists the roles, what each is made of, and which are assemblable now.