Consent layer for agentic payments

Your AI agent can spend.
You stay in control.

Delegate a budget in chat, approve it once, and your agent pays on its own, inside hard limits.

Payment approval SingIt via WhatsApp

Your agent research-agent wants a spending policy:

Merchant
api.websearch.dev
Max per payment
$0.05
Total budget
$1.00
Pay with
any token
Expires
Today, 18:00

Strict mode: every single payment asks for its own approval.

x402 crossed 169M agent payments. Every one of them was signed with keys a human handed to a machine. One bad prompt, one hijacked tool, and the wallet is gone.

Hand over your keys

The agent owns the wallet. Forever, or until the first exploit.

Approve everything by hand

Then why have an agent at all?

Trust a backend limit

That is just trusting a different server with the same keys.

The missing piece is consent: a limit you actually signed.

How it works

policy.json

{
  "agent":         "research-agent",
  "merchant":      "api.websearch.dev",
  "maxPerPayment": "$0.05",
  "budget":        "$1.00",
  "payToken":      "any",
  "expiresAt":     "2026-07-18T18:00Z",
  "nonce":         "policy-7d41"
}

Canonicalized, hashed, signed. The agent never sees a private key.

  1. Delegate

    Tell your agent what it may spend, right in the chat: budget, merchant, expiry.

  2. Approve

    SingIt sends the policy to you on Telegram, WhatsApp, or iMessage. Strict mode asks again before every payment.

  3. Pay

    The agent settles x402 payments on its own, as long as they fit the policy.

  4. Prove

    Every payment carries the signed consent, so the merchant verifies both the money and the permission.

Crypto in. Real things out.

LLM credits

Top up API credits for the models your agent runs on, paid with any token in your wallet.

Gift cards & top-ups

A real catalog of products and mobile refills, delivered as codes straight to your chat.

Pay-per-use APIs

Any x402 endpoint on the open web, paid per request with whatever token you hold.

No KYC. No card on file. A wallet and a chat is all it takes.

Everything between intent and payment

A budget, not your keys

Approvals where you already are

No new app. SingIt reaches you on the channel you answer fastest.

  • Telegram
  • WhatsApp
  • iMessage

Hard limits

Budget, per-payment cap, merchant, purpose, expiry. The policy is the wall, not a suggestion.

maxPerPayment: 0.05
budget: 1.00
expires: 18:00

Pay with any token

Stables or anything else in the wallet. SingIt prices the swap and settles at real rates.

x402-native

402 Payment Required
↓ policy check
200 OK

Receipts for everything

Balances, history, and the consent proof for each payment, queryable from the same chat.

Give your agent a budget, not your keys.

Approvals in your messenger, hard limits in a signed policy, and strict mode when you want a say on every payment.

View on GitHub