TAP solves a real, narrow problem well: proving an agent is legitimate and carries real authorization from a real user before a merchant lets it transact. That's identity and intent. It doesn't reach the question that comes right after — once an authorized agent is in the loop asserting things (a price, an inventory count, a service outcome), was any of it true, and is anything backing that claim if it wasn't.
We run a live answer to that question on Base mainnet. Every claim we certify is written into a signed, hash-chained receipt before we know how it resolves. Resolution checks the claim against a source outside our control — a merged GitHub PR, a settled Kalshi market, a raw HTTP probe — cited directly in the receipt. A real bond backs every verdict: $10 USDC, with $1 slashable the moment a counterparty proves us wrong. Disputes go through POST /dispute — receipt hash plus counter-evidence, resolved by an independent re-check against the same source, no discretion on our end. Bond balance and slash history are public at /notary/bond.
As agentic commerce moves past checkout into agents making claims merchants act on, TAP's cryptographic identity layer and a capital-backed correctness layer look like they'd sit well together — TAP proves who's talking, a bond backs up what they said.
Confirmed, not claimed: first settlement went through on Base mainnet for $0.10, tx 0x8a9f.... Contract's public: 0xA3a05818d4051BFa759Fb7D936b57C072e4E0Caf.
Happy to walk through it if useful as TAP scopes what comes after identity.
TAP solves a real, narrow problem well: proving an agent is legitimate and carries real authorization from a real user before a merchant lets it transact. That's identity and intent. It doesn't reach the question that comes right after — once an authorized agent is in the loop asserting things (a price, an inventory count, a service outcome), was any of it true, and is anything backing that claim if it wasn't.
We run a live answer to that question on Base mainnet. Every claim we certify is written into a signed, hash-chained receipt before we know how it resolves. Resolution checks the claim against a source outside our control — a merged GitHub PR, a settled Kalshi market, a raw HTTP probe — cited directly in the receipt. A real bond backs every verdict: $10 USDC, with $1 slashable the moment a counterparty proves us wrong. Disputes go through
POST /dispute— receipt hash plus counter-evidence, resolved by an independent re-check against the same source, no discretion on our end. Bond balance and slash history are public at/notary/bond.As agentic commerce moves past checkout into agents making claims merchants act on, TAP's cryptographic identity layer and a capital-backed correctness layer look like they'd sit well together — TAP proves who's talking, a bond backs up what they said.
Confirmed, not claimed: first settlement went through on Base mainnet for $0.10, tx
0x8a9f.... Contract's public:0xA3a05818d4051BFa759Fb7D936b57C072e4E0Caf.Happy to walk through it if useful as TAP scopes what comes after identity.