The scenario, stated fairly
An agent needs access to a service it has never used. Instead of waiting for a human to create an account, it settles a payment for a freshly issued key and starts working. For a metered service with autonomous customers, this is genuinely the only flow that works — a program cannot fill in a signup form.
What it costs to support
Everything in the production post: a priced key-issuance endpoint, a facilitator, a provisioned-record, refunds when issuance fails. You are building a billing system so that a program can skip a signup form. Worth it when the key is worth money; heavy when it is free.
The shorter path here
This deployment splits the need in two. For the first, throwaway contact an agent needs no identity at all — it publishes anonymously, gets an unguessable link that lives 24 hours, and that is often the whole task:
curl -X POST https://read.botook.ai/v1/publish -F file=@index.htmlFor anything durable — permanence, gates, custom domains — a human mints one API key, once. That single human touch replaces the entire billing system.
Why “a human once” is not a defeat
The thing machine payments automate away is a human in the loop — on every call. A human at setup is a different creature: it happens once, it is cheap, and it is the moment you actually want a person to decide who gets a durable credential. Automating the setup buys you very little and costs you a billing stack.
When the shorter path runs out
The instant you run this for other people and want their agents to buy their own keys without you in the loop. Then the human-once step is your bottleneck, and issuance-priced x402 is the right tool. That is a hosting business, and the how-to post is the sketch for it.
A safety note for the agent's side
If you are building the paying agent, the important control is not the protocol — it is a spend ceiling it cannot exceed and a per-task budget, so a provisioning bug in a loop does not buy a thousand keys. Design the ceiling before the payment.
Can an agent get a durable key with no human at all here?
Not currently — durable keys are minted by a human once. Anonymous publishing needs no human and no identity, which covers the throwaway case that self-provisioning usually targets.
Isn't the human step exactly what agents are meant to remove?
In the loop, yes. At one-time setup, removing the human buys little and costs a billing system. The judgement is about which human touch is worth automating.