Sample data. Mockup. Not a real account or verdict.
leash
A SPENDING LIMIT FOR AI AGENTS

Give your AI agent a budget, not your wallet.

Leash puts an AI agent’s money behind hard limits that are enforced on the blockchain. Anyone, including your partners, can check those limits in under a minute. No wallet, no account.

SAMPLE · like a company card for an AI
NFT AI owner agent limits in between
Per payment limit0.25 NEAR
Per period limit0.5 NEAR
Approved payees2 accounts
Emergency freezea guardian can pause
Who is in chargethe NFT holder

The four questions people ask.

Can the agent run off with everything?

Not past its limits. Each payment and each period has a hard cap written into the contract.

Who is in charge?

Whoever holds the NFT. Transfer the NFT and control moves with it.

What if something looks wrong?

A guardian can freeze the agent. Loosening limits has to wait out a delay first.

Can I check this myself?

Yes. Paste the address. The check runs in your browser against a public data source.

Where teams could use it.

These are ideas, not customer claims.

A treasury assistant

An agent that pays routine invoices without ever holding the whole treasury.

Vendor payments

Pay only approved accounts, up to a set amount each time.

Trading with a loss cap

Let an agent trade while the worst case stays a known number.

Partner pilots

Hand a partner a one-page check instead of a technical walkthrough.

A check tells you

✓ The agent has one restricted key

✓ The code matches what was published

✓ What the limits are right now

A check does not tell you

✕ That the code is free of bugs

✕ That the data source is honest

✕ That the published files are genuine

GOOD TO KNOW

Each agent key has a fuel tank.

A key funded with 0.25 NEAR covers about 8 payments at the default setting, then it needs replacing. Every check shows how much is left. estimate

Send a check to a partner.

A one-page report with the answers above, in plain words. export available

For engineers: technical report, command-line checker and source. Real-time cryptographic verification on NEAR Protocol.

as of block 123456789 · 2026-10-26T09:14:02Z · read-only · verdicts are relative to release.json

✓ KEY STRUCTURE VERIFIED

Proves key structure and that the deployed code matches the published build. Does not audit the contract logic. Computed by this page against one RPC provider; re-run the CLI and make repro to check independently.

▾ checks.out
1✓ keys pass
2✓ code hash pass
3✓ nft keyless pass
4✓ interface pass
▾ keys.json
1{
2 "public_key": "ed25519:7Hq2…Lm4P",
3 "permission": { "FunctionCall": {
4 "receiver_id": "agent.test.near",
5 "method_names": ["spend"],
6 "allowance": "250000000000000000000000"
7 } }
8}

✓ all key rules pass

About 8 calls at 30 Tgas attached. The allowance is not refunded, so each call drains about 0.0289 NEAR (sandbox measurement, approximate). below 20 reservations

▾ spend.meter
0.2 / 0.5 NEAR

Cap enforced over any window of period minus one bucket. The contract returns only the window total, so no per-bucket history is shown. Max loss before detection: 0.5 NEAR (approximate).

▾ hash.diff
1- published EcqwWyLjBymr9s34H7T5hovyc69TTaH8MDok9LXookBd
2+ computed EcqwWyLjBymr9s34H7T5hovyc69TTaH8MDok9LXookBd

All 44 characters match.

▾ nft.json
1contract nft.test.near
2token_id token-1
3owner owner-sample.testnet
4keys 0 // keyless
▾ owner_slot
1// get_owner_slot, chain time 2026-10-26T09:14:02Z
2Withdraw { amount: 0.5 NEAR }
3proposer owner-sample.testnet
4earliest execute in 2h 10m
5expires in 26h 10m
6// guardian: the central trust assumption of this design
▾ claims.diff
1+ key structure at the pinned block
2+ deployed wasm equals the published build
3- the contract logic is safe
4- the RPC is honest
5- release.json is authentic
✓ SCENARIO A: Legitimate Operation Within Cap

0.2 NEAR transfer to demo-bob.test.near. All 8 guards pass. Net gas burnt: 4.38 TGas. Transaction confirmed.

▾ execution.trace 

          

        

      

    

  


  
  

    

      
▾ release.json

      

        

          

        

      

    

  


  
  

    

      
▾ limits.md

      

        

          
Gas and Allowance Reservation Bounds

          

            In NEAR protocol, FunctionCall access keys with allowances reserve the full attached gas fee upfront from the allowance.
            Unlike on-chain execution where unused gas is refunded to the account balance, access key allowances are never refunded.
          

          
1Attached Gas: 30 Tgas

          
2Upfront Key Reservation: ~0.0289 NEAR per call

          
3Key Allowance: 0.25 NEAR -> ~8 invocations capacity

          
4Key Allowance: 1.00 NEAR -> ~34 invocations capacity

          
5Window Cap: Enforced per sliding period minus one bucket