Prediction Integrity · Demo
Certify an AI prediction before the outcome is known
Submit a prediction payload and receive a real Ed25519-signed certificate. The demo uses the BetFire AI reference integration as the prefilled sample — edit any field to test your own shape.
The signature is cryptographically real. The signing key is separate from the production root. Records are sandbox-scope and non-authoritative.
Prediction payload
Prefilled with the BetFire AI reference integration. Edit any field and submit to receive a real Ed25519-signed certificate.
Stable identifier for the platform issuing the prediction.
Unique identifier within the source platform.
Identifier of the model that produced the forecast.
ISO-8601 timestamp captured when the prediction was generated.
Short human-readable description of what was predicted.
The actual prediction claim. Bound into the signed payload.
Whether the outcome has been observed and resolved.
Demo signing key (cd_demo_2026). No production registry write. Records are non-authoritative.
How the demo works
The form is prefilled with the BetFire AI reference integration so the demo has a real shape to sign. Every field is editable.
Submit. The server canonicalizes the payload using RFC 8785 JSON Canonicalization Scheme, producing deterministic bytes for hashing.
The canonical bytes are hashed. The fingerprint is unique to this prediction at this moment — any byte change produces a different hash.
CertifiedData signs the canonical payload using the demo signing key (cd_demo_2026). The signature is non-authoritative but cryptographically real.
The result page shows the signature and points to the demo public key at /.well-known/demo-signing-keys.json. Anyone can verify offline.
Sandbox scope
The demo signs with cd_demo_2026 — a key separate from the production root. Production verifiers reject any artifact whose key_id appears in the demo registry.
The demo endpoint signs in memory and returns the certificate without writing to the canonical artifact registry. Records are non-authoritative.
30 requests per minute per IP. The endpoint is anonymous — no account, no API key — but the rate limit protects the demo signing oracle from abuse.
The signed payload uses the prediction_receipt.v1 schema. Adopt it as-is for production by switching to the authenticated /api/notary/create flow with the production signing key.
Machine-readable summary
{
"concept": "Prediction Integrity demo",
"concept_type": "interactive-demo",
"canonical_url": "https://certifieddata.io/prediction-integrity/demo",
"parent_concept": "Prediction Integrity",
"demo_endpoint": "POST /api/prediction-integrity/demo",
"demo_rate_limit": "30 requests / minute / IP",
"demo_auth": "none (anonymous)",
"signing_key_id": "cd_demo_2026",
"public_key_url": "/.well-known/demo-signing-keys.json",
"signing_algorithm": "Ed25519",
"hash_algorithm": "SHA-256 (RFC 8785 canonicalized)",
"payload_schema": "prediction_receipt.v1_demo",
"persistence": "none — in-memory signing, no DB write",
"production_path": "Adopt the same payload shape with the authenticated POST /api/notary/create endpoint and the production signing key."
}