GUIDE / PROTOCOLS
What do the protocols do?
Some handle payment. Others handle permission or messaging. None gives a complete view on its own.
| Layer | Role | What we can see |
|---|---|---|
| x402 | Pay to access an online service. | A payment record alone does not show what was requested or delivered. |
| AP2 | Record permission for an agent to pay. | Permission records are private. No AP2 feed is connected here yet. |
| MPP | Handle payments between machines and services. | A Tempo transaction is not automatically an MPP purchase. |
| A2A / MCP | Let agents communicate or use tools. | A message or tool call does not prove a payment or successful result. |
| Tempo network | Record transactions on a blockchain. | Connected. We collect finalized records; history has gaps. |
| Exchange / venue | Where a trade takes place. | Named only when the transaction evidence supports it. |
Why no single feed sees everything
Blockchains expose payments. Buyer requests and seller outputs often stay private. Seeing more requires direct connections to the services involved.
How to compare activity fairly
Compare the same dates, network and currencies. Keep fees separate and remove duplicate payments before adding totals.
What is connected today
Tempo records, an x402scan sample and MPPscan service totals are connected. Stripe collects private events from our own account. AP2, A2A, MCP, UCP and ACP intake is ready for authorized applications; no participating feeds are active yet.