- receipt
- loading…
- tool
- loading…
- outcome
- loading…
- charged
- loading…
- permit
- loading…
- idempotency
- loading…
- issued
- loading…
- key
- loading…
Portable receipt / Public evidence
Verify this receipt yourself.
This receipt is self-issued from a non-sensitive
partner.echo call and was issued on
.
It is a published historical sample: verifying it proves the gateway
path signed this receipt with the published key. It is not customer
evidence, and it is not a test of the deployment running today.
01 / Published artifact
Signed claims from the portable bundle.
Loading the published receipt and matching public-key snapshot…
Keep both files together. The receipt contains the signed bytes; the snapshot contains the matching Ed25519 public key.
Download receipt.json Download trust-keys.json Download verify_receipt.py02 / Offline verification
Check the signed bytes fully offline.
Download the receipt, the key snapshot, and the standalone
verifier below. The downloads need no account and no key. After
the downloads, run the verification 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.
curl -fsSLO https://www.thisisatest.tech/proof/receipt.json
curl -fsSLO https://www.thisisatest.tech/proof/trust-keys.json
curl -fsSLO https://www.thisisatest.tech/proof/verify_receipt.py
python3 -m pip install cryptography
python3 verify_receipt.py \
--bundle receipt.json \
--keys trust-keys.json \
--expect-issuer https://api.thisisatest.tech
The verifier is a standalone script published on this page: it
checks the signature over the receipt's hashes using the supplied
key snapshot, with no account and no call back to the gateway.
Anyone with a source checkout can use the SDK CLI
b2a-verify-receipt instead. The same public key set
is also served live, with no key needed, at
https://api.thisisatest.tech/.well-known/trust-keys.json
(and
https://api.thisisatest.tech/.well-known/jwks.json).
Try the API
Two calls that need no key.
These read-only calls work with no account and no key. Get a free sandbox demo key at /demo-key/ with no account needed to try permits and the demo tool. Production keys are issued to design partners through the pilot contact below.
curl -sS https://api.thisisatest.tech/health
curl -sS https://api.thisisatest.tech/.well-known/trust-keys.json
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, email the tool scenario: the tool or action, what goes wrong when it is retried, and how you currently check whether it ran. Include the cost of one duplicate or unproven call, the budget owner, and a decision date. Synthetic or redacted examples only. The pilot is paid, bounded to one tool, and priced after fit is established, with setup and recurring service quoted separately in writing. A call happens only when a scenario needs one. Read the pilot scope and estimate economic fit.