Receipt verifier

Buyer-side verification for signed inference receipts. Pure Go, no runtime dependencies.

Status: Pending. Offline verification of current receipts is pending a verifier update. The released verifier (verify-v1.1.0) cannot parse the receipts buyers receive today: it rejects them with exit code 65 (unknown field "model_hash"). Its built-in default receipt-key host is also no longer valid, so do not rely on default key lookup. This page is kept as a reference for the flags and result semantics.

The verifier binary is macprovider-verify. It checks a signed receipt against the request and response you recorded, resolves the provider’s receipt key, and returns a deterministic valid, invalid, or inconclusive result. Some non-streaming responses carry a v0.3 receipt in the X-MacProvider-Receipt response header (currently roughly a quarter to a third). Streams never do. For the rest, use GET /v1/receipts. See Signed receipts.

Install

Releases are published on GitHub (Augustas11/macprovider) under tags named verify-v<version>. The current release is verify-v1.1.0.

macOS Apple Silicon

VERSION=1.1.0
gh release download "verify-v${VERSION}" --repo Augustas11/macprovider \
  --pattern "macprovider-verify-${VERSION}-darwin-arm64" \
  --pattern "macprovider-verify-${VERSION}-darwin-arm64.sha256"
shasum -a 256 -c "macprovider-verify-${VERSION}-darwin-arm64.sha256"
chmod +x "macprovider-verify-${VERSION}-darwin-arm64"
sudo install -m 0755 "macprovider-verify-${VERSION}-darwin-arm64" /usr/local/bin/macprovider-verify

macOS Intel

VERSION=1.1.0
gh release download "verify-v${VERSION}" --repo Augustas11/macprovider \
  --pattern "macprovider-verify-${VERSION}-darwin-amd64" \
  --pattern "macprovider-verify-${VERSION}-darwin-amd64.sha256"
shasum -a 256 -c "macprovider-verify-${VERSION}-darwin-amd64.sha256"
chmod +x "macprovider-verify-${VERSION}-darwin-amd64"
sudo install -m 0755 "macprovider-verify-${VERSION}-darwin-amd64" /usr/local/bin/macprovider-verify

Linux amd64

VERSION=1.1.0
gh release download "verify-v${VERSION}" --repo Augustas11/macprovider \
  --pattern "macprovider-verify-${VERSION}-linux-amd64" \
  --pattern "macprovider-verify-${VERSION}-linux-amd64.sha256"
sha256sum -c "macprovider-verify-${VERSION}-linux-amd64.sha256"
chmod +x "macprovider-verify-${VERSION}-linux-amd64"
sudo install -m 0755 "macprovider-verify-${VERSION}-linux-amd64" /usr/local/bin/macprovider-verify

The release also ships output.schema.json, the JSON Schema for --json output.

Usage (pending)

The verifier takes either a captured header value plus canonical prompt and output hashes (--receipt, --prompt-hash, --output-hash), or a bundle JSON file with the receipt, the OpenAI request body, the OpenAI response body, and optionally provider_id (--bundle). With the released 1.1.0 binary, both modes stop at the input-format error above for current receipts. Instructions will return here once an updated verifier ships.

CLI reference

Flag	Semantics
`--version`	Print `macprovider-verify <binary-version> (verifies up to SPEC-015 v<max-spec-version>)` and exit 0
`--help`	Print usage and all supported flags, then exit 0
`--bundle <path\|->`	Verify a bundle JSON file. `-` reads stdin. Cannot be combined with `--receipt`
`--receipt <value>`	Verify a raw receipt header value. Requires `--prompt-hash` and `--output-hash`. Cannot be combined with `--bundle`
`--prompt-hash <hex>`	Expected canonical prompt SHA-256 hex. Required with `--receipt`
`--output-hash <hex>`	Expected canonical output SHA-256 hex. Required with `--receipt`
`--pubkey <base64>`	Explicit base64 Ed25519 public key. Use it as the trust root for offline or air-gapped verification
`--provider-id <id>`	Provider id used to look up `/v1/receipt-keys/<provider_id>`. Required online unless `--pubkey` is given
`--json`	Emit exactly one line of JSON
`--offline`	Disable live network fetches. Needs `--pubkey` to reach `valid`
`--quiet`	Suppress stderr diagnostics. The exit code is unchanged
`--coordinator <host>`	Receipt-key host, or `MACPROVIDER_COORDINATOR` if set. The built-in default in 1.1.0 is no longer valid
`--explain`	After a `valid` result, print the trust-boundary text to stderr
`--catalog <path>`	Local signed model catalog, used to check the receipt’s `model_hash`. Cannot be combined with `--catalog-url`
`--catalog-url <url>`	Fetch the signed catalog. Cannot be used with `--offline`
`--catalog-pubkey <b64url>`	Ed25519 catalog signing key (43-character base64url)
`--catalog-pubkey-url <url>`	Fetch the catalog signing key. Cannot be used with `--offline`
`--require-model-hash`	Fail closed (exit 1) when the receipt’s `model_hash` is null

Environment

Env	Purpose
`MACPROVIDER_COORDINATOR`	Default for `--coordinator`
`MACPROVIDER_VERIFY_ALLOW_PRIVATE_COORDINATOR`	Set to `1` to allow loopback / RFC1918 receipt-key hosts

Running against a private receipt-key host

By default, --coordinator rejects literal loopback, RFC1918, link-local, and unspecified IP hosts. This stops you from verifying against a private endpoint when you expected the public one. For local development or an explicitly private deployment, set MACPROVIDER_VERIFY_ALLOW_PRIVATE_COORDINATOR=1. The guard checks literal IPs only. It does not block hostnames, so you are responsible for choosing trusted DNS names.

Input modes

Mode	Required flags
Header + hashes	`--receipt`, `--prompt-hash`, `--output-hash`, and `--provider-id` unless `--pubkey` is supplied
Bundle file	`--bundle <path>`. The JSON contains `bundle_version`, `receipt`, `request`, `response`, and optionally `provider_id`
Stdin bundle	`--bundle -` with the same JSON shape as bundle mode

--bundle and --receipt cannot be combined. --offline prevents live fetches. With --pubkey, a resolver failure cannot downgrade an otherwise valid explicit-key verification.

Exit codes

Code	Meaning
0	`valid`
1	`invalid`: bad signature or canonicalization, rejected pubkey, or a previous key used outside its grace window
2	`inconclusive`: pubkey unresolvable, `/v1/receipt-keys` 404, or stale cache with the live service unreachable
64	Usage error
65	Input format error (current receipts hit this in 1.1.0)
70	Internal software error

Version compatibility

Verifier	Receipt versions verified
1.0.x	0.2.0 – 0.2.4
1.1.x	0.2.0 – 0.3.3 as specified, but 1.1.0 rejects current v0.3 buyer receipts (exit 65)

1.0.x verifiers report v0.3 receipts as invalid. Neither release verifies the v0.4 settlement receipts the network uses internally. Those are never sent in buyer response headers. See Verified model settlement.

Trust boundary

A valid result proves two things: the tuple was signed by a holder of the provider’s receipt key, and the verifier resolved that key through the trust source you configured. It does not prove model honesty, timestamp honesty, response uniqueness, privacy, or replay resistance. See Security & trust model.

Litepaper

Getting started

Buyers

Providers

Network & trust

Guides index

Ledger

Receipt verifier

Receipt verifier

Install

macOS Apple Silicon

macOS Intel

Linux amd64

Usage (pending)

CLI reference

Environment

Running against a private receipt-key host

Input modes

Exit codes

Version compatibility

Trust boundary

​Receipt verifier

​Install

​macOS Apple Silicon

​macOS Intel

​Linux amd64

​Usage (pending)

​CLI reference

​Environment

​Running against a private receipt-key host

​Input modes

​Exit codes

​Version compatibility

​Trust boundary

Receipt verifier

Install

macOS Apple Silicon

macOS Intel

Linux amd64

Usage (pending)

CLI reference

Environment

Running against a private receipt-key host

Input modes

Exit codes

Version compatibility

Trust boundary