What you receive, file by file

The purchase delivers one JSON object with a files array. Every entry carries its path, byte count, SHA-256 hash and full UTF-8 contents. This list is generated from the archive that is actually served, so it cannot drift from what you get.

18 files, 78,678 bytes, product paid-api-playbook version 1.0.0.

How to verify it

Hash the entire response body and compare it against the X-Product-SHA256 response header. Then hash each file's content and compare with that file's sha256. Both checks should pass before you use anything.

What the parts do

The playbook is the procedure to follow. The execution plan is the same procedure as JSON with explicit pass and stop conditions per step, so an agent can run it without re-reading prose. The template is a runnable Node.js x402 server with tests covering the paywall's failure paths. The calculator does exact-arithmetic unit economics in USDC micro-units. The worked example applies all of it to one small service.

See also the integration guide and a worked purchase with real numbers.