Tiba

Tiba / v0.1 / test network only

A signed permission slip for AI agents, and a signed receipt for everything they do, that anyone can check.

Agents are starting to act and pay on our behalf; nobody can prove what they were allowed to do.

See a real run Read the spec

An open extension to MCP and A2A. Built to sit beside the protocols agents already use.

Portable proof, not a central service
01
Mandate scope · budget · expiry
02
Guarded action allow or refuse before it runs
03
Receipt signed · portable · checkable

How it works

Permission first. Proof after.

Tiba keeps the permission and the evidence with the action — so a tool provider, auditor, merchant, or another agent can inspect it without calling Tiba.

  1. 01

    Permission slip

    A signed mandate says exactly who may act, what they may do, for how long, and up to what budget.

  2. 02

    Guarded action

    A guard checks the mandate before a tool call or payment runs. A denied request still gets a signed audit record.

  3. 03

    Receipt anyone can verify

    The agent signs what happened. The full mandate chain travels with the receipt and can be checked offline.

A real run

Six steps, four signed receipts, one independently checked result.

This is the public record from 13 September 2026. It used Solana devnet (test network) — never mainnet or real funds.

The historical mandate has expired. The artifact viewers below preserve the exact signed records; they are not a live authorization.

  1. 1

    Policy

    Mandate signed

    A narrow draft was displayed and a human entered literal SIGN before the mandate was signed.

    Mandate
    mandate:f95975e7-cbbf-4f9e-94e0-3a44c7c50b23
    Budget
    0.001 USDC
  2. 2

    MCP / allowed

    A scoped note write was allowed

    The guard allowed notes.write and signed a success receipt.

    View signed receipt success 
    Loading receipt…
  3. 3

    MCP / blocked

    An out-of-scope call was stopped before forwarding

    notes.delete was outside the mandate. The guard refused it and signed the denial TIBA_SCOPE_DENIED.

    View signed receipt denied 
    Loading receipt…
  4. 4

    Payment / success

    0.001 USDC was paid on Solana devnet (test network)

    The payment guard checked the mandate before sending the transfer. The chain record is available independently in the Solana explorer.

    Solana devnet transaction 5qYpts…PtZFB
    View signed receipt success 
    Loading receipt…
  5. 5

    Revoked / refused

    The mandate was revoked; the next action was refused

    A signed revocation list ended the permission. The next notes.write was stopped with TIBA_REVOKED.

    View signed receipt denied 
    Loading receipt…
  6. 6

    Independent check

    A separate verifier checked all four receipts

    A separate Python process received only the public agent did:key and the receipt files. It verified all four signed records.

    View independent verification result ok 
    Loading verification result…

Check a receipt yourself

Verify the signature in your browser.

Paste a Tiba v0.1 receipt. This page decodes its did:key, checks it is an Ed25519 key, and verifies the receipt signature locally. Nothing is uploaded.

Cryptographic signature and embedded signer key only. It does not establish signer identity or trust, schema compliance, current revocation, settlement, or authorization status.

Pre-filled with the allowed note-write receipt from the real run.

Ready to verify

Uses the browser’s built-in Ed25519 cryptography.

The tampered example changes a signed field. Its signature should fail.

For developers

Use the verifier. Keep your protocol.

Tiba is an envelope and evidence layer, not a replacement for payment, tool, or agent-to-agent protocols.

Quickstart

Run the reference checks

npm install
npm run test

Requires Node 22+ and Python 3.10+.

TypeScript

@tiba/verifier

Dependency-free v0.1 verifier for Node. It creates, signs, and verifies Tiba objects.

Read verification rules

Python

tiba-verifier

Independent verifier package using cryptography. Its CLI can check a bundle with the public actor DID.

Read verification rules
SpecificationTiba Agent Mandate and Execution Receipt v0.1 Mandate schemaJSON Schema 2020-12 Receipt schemaJSON Schema 2020-12 Revocation schemaJSON Schema 2020-12
System It handles Tiba adds
Google AP2 Payment mandates and checkout evidence only. Agent-to-agent delegation and non-payment action receipts are outside AP2’s scope. Tiba adds that portable evidence; AP2 payment credentials stay in AP2.
x402 HTTP payment requirements and settlement. A pre-payment policy check, spend accounting, and a receipt for the whole action.
Visa TAP Visa-network-specific trust signals and HTTP signatures. Network-neutral evidence for any tool or action. TAP rules stay TAP’s job.
MCP Agent-to-tool calls and tool semantics. A mandate guard around a tool call and a receipt in its metadata.
A2A Agent discovery, tasks, and messages. A portable mandate-chain and receipt extension with strict sub-delegation.

Honest limits

v0.1, test network only.

  • did:key proves control of a key, not a person’s legal identity or a merchant’s legitimacy.
  • Production needs a fresh signed revocation source and a shared atomic ledger for global spend safety.
  • A receipt records what its signer attests. Verify settlement evidence with Solana, x402, AP2, TAP, or the relevant system.
  • Tiba does not make an unsafe server safe by itself; the guard must be on the real execution path.