OceanAltOceanAlt

Cap what your AI can spend

An AI that spends money doesn't hesitate. It just does it. So you set the rules: how much per payment, how much per day, who it may pay. Anything beyond is declined on the spot, and one click stops everything on our side.

Step 1 · Set the rules

Like an allowance: set the caps and the purpose. Anything beyond that will not go through.

Who is it allowed to pay?

What this key is

  • · It cannot touch your wallet and never sees your private key. All it can do is request payments within the rules above.
  • · If it leaks, whoever has it is still capped by your limits and allowlist. Keep the limits small.
  • · You can stop it at any time, and that takes effect immediately.

Pick who it's allowed to pay first.

Step 2 · Get your key and keep it safe

Your key appears here once created. The secret is shown only once, so save it right away.

Step 3 · Where my money went

No records yet. Once your AI pays with this key, allowed and blocked attempts show up here.

What do I do with the key?

Configure the key in your AI or script so it asks us before each payment. We judge it against your rules for compliance, limits, payee and purpose, and only return allow if all pass.

How your AI pays

curl -X POST "https://oceanalt.com/api/pay" \
  -H "content-type: application/json" \
  -H "x-agent-secret: $OCEANALT_AGENT_SECRET" \
  -d "{"agentId":"$OCEANALT_AGENT_ID","amountUsdc":1.5,"to":"0x…","purpose":"buy API credits","nonce":"$(uuidgen)"}"

Only decision=allow means it went through; a block tells you which gate stopped it (limit / payee / purpose / compliance). Full docs →

Looking for the other kind of key? This page caps what your AI may spend. If you want higher limits on how much you can call us, that's an API key. Go there →

How far we can go for you

  • ① See it — Watch an address, get alerted. Zero integration. Use it →
  • ② Stop it — This page. Your AI asks before paying, and anything over the limit is declined on the spot. available now (pre-settlement decision)
  • ③ Make it impossible — Rules written into an on-chain contract: an over-limit payment reverts on-chain and never reaches the payee. No server of ours is in the path, and we hold no privileges over it (non-custodial). testnet · unaudited · see it live →

Two things to know before you rely on it:

  • ① We make a pre-settlement decision; we do not hold or move funds. Your AI asks us before each payment and we return decline if it breaks your rules; the money always leaves its own wallet, and we never touch your funds (settlement on the public endpoint is recorded as simulated, tx=simulated). A decision protects only payments that ask and act on it; for anything that skips the check or ignores a decline, ① address alerts are the backstop, and they arrive after the fact.
  • ② To have the rules enforced rather than merely judged, use ③: limits written into an on-chain contract, where an over-limit payment fails on-chain without passing through any server of ours. Testnet only for now.