Receipt
Cryptographic decision receipt — an Ed25519 signature over canonical hashes of the request + response of a single forecast call. Anyone with the published public key (see /.well-known/blackwall-signing-keys.json) can verify offline without contacting Black_Wall. We sign and store HASHES ONLY — the raw request/response bodies are never persisted on our side. To verify later, you (or your auditor) provide the bodies and we re-hash to check against the signed envelope.
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Receipt's own UUID (distinct from forecast_id). |
| forecast_id | string | The forecast this receipt vouches for. |
| issued_at | string | |
| algorithm | string | |
| key_id | string | Which signing key was used. Look it up in /.well-known/blackwall-signing-keys.json. Receipts issued before a key rotation continue to verify against the retired key. |
| request_hash | string | SHA-256 (hex) of canonical(request_body), prefixed `sha256:`. |
| response_hash | string | SHA-256 (hex) of canonical(response_body without receipt), prefixed `sha256:`. |
| signature | string | Base64url Ed25519 signature over the canonicalized envelope (minus signature). |
| verify_url | string | Convenience URL for POST verification. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/blackwalltier-com/json-schema/blackwalltier-com-receipt-schema.json",
"title": "Receipt",
"description": "Cryptographic decision receipt — an Ed25519 signature over canonical\nhashes of the request + response of a single forecast call. Anyone\nwith the published public key (see /.well-known/blackwall-signing-keys.json)\ncan verify offline without contacting Black_Wall.\n\nWe sign and store HASHES ONLY — the raw request/response bodies are\nnever persisted on our side. To verify later, you (or your auditor)\nprovide the bodies and we re-hash to check against the signed envelope.\n",
"x-generated": "2026-10-29",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/blackwalltier-com-openapi.yaml#/components/schemas/Receipt",
"type": "object",
"required": [
"id",
"forecast_id",
"issued_at",
"algorithm",
"key_id",
"request_hash",
"response_hash",
"signature"
],
"properties": {
"id": {
"type": "string",
"description": "Receipt's own UUID (distinct from forecast_id)."
},
"forecast_id": {
"type": "string",
"description": "The forecast this receipt vouches for."
},
"issued_at": {
"type": "string",
"format": "date-time"
},
"algorithm": {
"type": "string",
"enum": [
"ed25519"
]
},
"key_id": {
"type": "string",
"description": "Which signing key was used. Look it up in\n/.well-known/blackwall-signing-keys.json. Receipts issued before\na key rotation continue to verify against the retired key.\n"
},
"request_hash": {
"type": "string",
"description": "SHA-256 (hex) of canonical(request_body), prefixed `sha256:`."
},
"response_hash": {
"type": "string",
"description": "SHA-256 (hex) of canonical(response_body without receipt), prefixed `sha256:`."
},
"signature": {
"type": "string",
"description": "Base64url Ed25519 signature over the canonicalized envelope (minus signature)."
},
"verify_url": {
"type": "string",
"format": "uri",
"description": "Convenience URL for POST verification."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/blackwalltier-com-receipt"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.