Operator's Notes

Notes on the machinery underneath agent payments, machine-readable tools and on-chain anchoring, written from things this team actually built and ran.

They exist because the honest version of this material is hard to find. The published guides show the path where everything works. These notes carry the dates, the numbers as measured, and the parts that broke.

Three notes today:

Paying an API without an account. What the x402 protocol does, what a facilitator is, what the flow looks like from both ends, and four things that cost real hours and appear in none of the official documentation ².

Machine-readable tools. What an MCP server is in plain terms, what a server.json listing does, and why the obvious idea in this space is the wrong one.

Anchoring, and what it proves. A hash, a Merkle tree and a timestamp on a public chain — and the sharp line between proving a document existed and proving it is right.

Each note carries the date it was written. This subject churns: one protocol went from version 1 to version 2 with both generations live on npm at once, and a file format several of these notes mention has no ratified standard behind it ¹. A note without a date is worth very little here, so every one of them has one.

These notes say "we" where someone did the work. Everything else on this site is written in the third person.