Your AI can't spend
without a sign-off.
Give an AI agent money to spend and you're trusting it not to go wrong. Spend Gate takes that on trust away. The agent asks sebbi.pro before every payment, it's checked against the limits you set and scored by the engine, and you get back a signed yes or no. Over the limit, wrong payee, acting out of line? No signature. No spend.
sebbi.pro is the sign-off, never your wallet. It never holds your money or the keys to it. It signs the decision; your own payment system releases the money only if the signature says yes.
Try it
A live agent with a £100-per-payment limit and a £250 daily cap. Paste your sebbi.pro key, or just watch the decisions — every one is sealed and provable.
How your code uses it
One call before the agent pays. Release the money only on an approved, spendable token.
POST https://sebbi.pro/x/spendgate/request
{ "api_key": "YOUR_KEY", "agent": "billing-bot",
"amount": 49.99, "payee": "AWS", "reason": "monthly compute" }
-> { "decision": "APPROVED", "token": "sbg1.…", "expires_utc": "…" }
release the payment, then POST /x/spendgate/confirm { token }
-> { "decision": "DENIED", "reasons": ["over the per-transaction limit"] }
do not pay
Anyone can check a token's signature against the published key, with no call to us: /x/continuity/pubkey. Or let an AI assistant run it all — connect https://sebbi.pro/mcp and ask it to gate a payment.
Why it holds
Per-payment limit, daily cap, an allow-list of who can ever be paid. Per agent.
Every payment is scored by the live engine and checked against your rules before a penny moves.
A short Ed25519-signed token, valid once, for a few minutes. Anyone can verify it.
Every approval and refusal is in the chain and provable against Bitcoin.