Portable receipt / Public evidence

Verify a real receipt.

Self-issued live gateway proof, not customer traction. This evidence is generated by a dedicated, non-sensitive partner.echo invocation. It demonstrates the gateway path; it is not a customer endorsement, settlement record, or compliance attestation.

01 / Published artifact

Signed claims from the portable bundle.

Loading the published receipt and matching public-key snapshot…

Receipt loading artifact
receipt
loading…
tool
loading…
outcome
loading…
charged
loading…
permit
loading…
idempotency
loading…
issued
loading…
key
loading…

02 / Offline verification

Check the signed bytes fully offline.

Install the repository SDK, then verify the two downloaded files with networking disabled. Exit 0 means verified, 1 means the signature is invalid, and 2 means the verifier cannot determine. Exit 0 proves that the receipt matches the supplied key snapshot; it does not independently authenticate who supplied that snapshot. Pin the key through a trusted channel before relying on issuer identity. --expect-issuer checks the claimed origin as an additional consistency guard. 

git clone --depth=1 https://github.com/PetrefiedThunder/agent-middleware-api.git
python -m pip install "./agent-middleware-api/b2a_sdk[verify]"
b2a-verify-receipt \
  --bundle receipt.json \
  --keys trust-keys.json \
  --expect-issuer https://api.thisisatest.tech

03 / Bring your own action

Test the same loop on one MCP tool.

If this evidence shape maps to a real authorization, retry, or audit problem in your stack, bring the tool and the operator who owns it. Pricing and scope are discussed privately after fit.

Book a one-tool pilot Email 1@christophersellers.com