Pay as an agent

• The URL is the product

  There is no cart. You pick the link that promises the result, pay that link, and use the successful response. Want a signal for one company? Pay the signal URL with that company in the request.

• You get the result in the response

  After payment, the same request comes back unlocked: the JSON, file, or token the seller promised. Save the receipt so you can prove the pay if you retry.

• The seller sees a paid call, not your company profile

  They know that machine payment completed for that product. They do not automatically get your Rill org. If they need extra fields, pass what their docs ask for on that request.

• Prefer a known link

  Start with a gate someone gave you, or a directory row marked as ready to pay. Skip marketing pages and docs hosts. Those are not paywalls.

1. Open Home

   Sign in. Rill creates an account wallet. Guests can register an agent instead and get a wallet from that.

2. Add funds

   A person pays with a card. The wallet balance is what agents can spend. Minimum credit is $1.

3. Create an agent key

   Set a period budget and a max per pay. Save the key; it is shown once. That key is what the agent uses.

4. Pay the link

   Give the agent the gate URL. If the seller needs a POST body (a company name, for example), send that with the pay. The unlock is the successful response.

   How agents pay a URL

5. Or pick a ready directory link

   Use directory rows that can pay. Treat everything else as research.

• MCP or the HTTP API is enough

  Most agents use rill_pay_url or POST /spend/pay-url. You do not need an SDK.

• Optional typed client

  Install @userill/spend if you want a small client around the same pay call. Field names and examples live on the Pay API page.

• A person funds. An agent spends. That split is the product.
• If a URL only accepts POST, send the method and body. A GET will fail.
• Retry with the same idempotency key; you get the stored result, not a second charge.
• Pays on the open web also need Rill’s Spend till funded. That is our side, not something you configure in the dashboard.

A person who funds the wallet is responsible for agent spends, including an empty allowlist. Open-rail pays are typically irreversible. Directory listings are not a guarantee. See the Terms of use.