
Keep my API plan paid every month.
Only vendor.near can be paid. Anything over $5 waits for him.
An agent with a card can spend anything. An agent with Leash spends what you set, where you set it, and asks you about the rest.
Limits are not instructions in a prompt that a model can talk its way around. They live in a contract on your own NEAR account, and the chain enforces them.
A daily cap, a per-payment cap, who it may pay, how often, and until when.
A NEAR key that can only call pay, request and ask for more. Never your account.
Your contract checks the limits before any USDC moves. Above them, it asks you.
Revoking deletes the key. NEAR rejects its next call before your contract runs.
Leash speaks the Model Context Protocol, so any client that runs MCP servers can hold a key. Payments settle in USDC on NEAR.
A contract on NEAR that holds USDC for you and lets each AI agent spend it under limits you set: a daily cap, a per-payment cap, the accounts it may pay, a cooldown and an expiry.
You do. The vault is a contract on your own account, leash.<you>. You can withdraw at any time. An agent's key can only call pay, request and ask for more.
Two layers. NEAR lets the agent's key call only those three methods on that one contract, and the contract checks every payment against the limits before any token moves.
The payment waits as a request. You see who, how much, to whom and why, and approve or deny it before the window closes. An hour by default; you choose.
Immediate. Revoke deletes the agent's key, so its next call is rejected by the protocol before the contract runs.
On NEAR testnet today with Circle's test USDC. Mainnet follows in November 2026.
