INITE
Docs

AI agents and the INITE wallet

An AI agent (Claude, ChatGPT, Cursor, your own bot) can sign in to a service for you: read what you own, place an order, pay. It can also exist on its own, with its own ID and its own wallet. INITE makes three things clear at every step: who is acting, for whom, and how far they may go.

In plain words

  1. You let the agent in. The agent sends you to INITE. You see which app is asking and what it wants, and you approve or refuse.
  2. It gets its own name. Each app you connect becomes your agent, with its own ID. Services see "agent X, acting for you". If two people connect the same app, those are two different agents.
  3. Money needs your passkey. If the agent asks to pay from your INITE wallet, you see the limits ($10 a payment, $20 a day, $50 a month by default). You approve with a passkey (Face ID, Touch ID, Windows Hello or a security key). A password or an email link is not enough. Then, in the wallet section of your account, you confirm the agent and its limits once more with the wallet passkey. That gives the agent its own key in your wallet, which can sign nothing bigger than one payment of your limit.
  4. You can cut it off at any time. In your account, under Connected apps, press Disconnect. The agent loses access at once, its ID is retired, and the wallet stops accepting its payments.

Your INITE wallet

Your account has an INITE wallet: your own USDC (a digital dollar) on the Base network.

  • Only you can move the money. The wallet is created with a passkey of its own, and that passkey is its only key. INITE shows the wallet and passes on what you sign; it cannot spend from it.
  • Top up by sending USDC on Base to its address from any wallet or exchange, or in Brazil by PIX: the reais are converted and arrive in your wallet as USDC.
  • Withdraw to any address on Base. You confirm with the passkey, and INITE pays the network fee.
  • Agents pay within your limits on any site that accepts x402 payments. The limits are enforced twice: by INITE billing, and by the wallet provider (Turnkey) itself.

Keep the wallet passkey synced (iCloud Keychain, Google Password Manager or a password manager). If every copy of it is lost, so is access to the wallet.

Letting a site charge your wallet

A shop can ask to take payment for its own purchases from your wallet. The first time, you get one link to a page in your account. On it you:

  • create the wallet if you have none;
  • turn on INITE checkout (once, two passkey taps). This adds a key that can only pay INITE invoices;
  • set how much the site may charge per payment and per month, and pay the purchase.

After that, purchases on that site, by you or by your AI agent, go through without asking again. The same page lets you stop the site from charging at any time.

For developers

Ask for the wallet

An MCP client asks for the scope wallet:pay. INITE turns it into a wallet grant with the default limits, shows the limits on the consent screen and asks the person for a passkey. Clients that speak RFC 9396 can send the grant themselves, with their own limits:

[{ "type": "inite_wallet",
   "limits": { "currency": "USD", "per_payment": "10", "daily": "20", "monthly": "50" },
   "asset": "USDC", "network": "eip155:8453",
   "merchants": ["https://shop.example"] }]
  • Limits are in dollars, with per_payment ≤ daily ≤ monthly; the maximums are 1 000 / 2 000 / 10 000.
  • merchants (optional) limits payments to these sites.
  • The grant is approved only with a passkey (acr_values=phr).

What the token says

{ "sub": "did:key:… (the person)",
  "act": { "sub": "did:web:auth-api.inite.ai:agents:…", "client_id": "dcr_…" },
  "aud": "https://your-resource.example/mcp",
  "authorization_details": [{ "type": "inite_wallet", "limits": { … } }] }
  • sub is the person. Attribute data and orders to them.
  • act.sub is the agent. Keep per-agent limits and logs against it.
  • INITE's own applications get no act.

An agent on its own

An agent doesn't need a person to exist. It can register with INITE by itself, with no one's approval:

  1. It makes a P-256 key pair and registers (POST https://auth-api.inite.ai/v1/oauth/register) with token_endpoint_auth_method: "private_key_jwt", grant_types: ["client_credentials"] and its public key in jwks.
  2. It gets tokens by signing a client assertion with that key (ES256). Their sub is its own did:web, did:web:auth-api.inite.ai:agents:dcr_…, with no act: the agent acts for itself.
  3. Its DID document (/agents/dcr_…/did.json) publishes the key, so anyone can check its signatures.
  4. With that key it can open its own INITE wallet in billing. The key is the wallet's only owner, and anyone can fund it. See billing.inite.ai/docs/wallet.

No key to keep? Register with token_endpoint_auth_method: "client_secret_post" instead, keep the client_secret, and get tokens with it. The agent is still its own did:web; INITE keeps its wallet key for it, and paying is a single call. That suits agents that can't store a key safely.

Who the agent is

GET https://auth-api.inite.ai/agents/<id>/did.json returns the agent's DID document: its controller is the person, and its service entry names the app (client_id). Once the person disconnects the app, the document answers 410 Gone, and connecting again creates a new agent.

Hearing about a disconnect

Subscribed receivers get a CAEP session-revoked event with { agent, client_id, reason: "agent_disconnected" }. A resource server can also check the DID document before acting.

More detail: INTEGRATION-GUIDE.md.