Skip to content

Changelog

Version history, new features, and improvements to the BlueFox Edge API.

v2.0.0October 2026
  • Brand safety: who answered (October 2026): every POST /safety/check and /safety/check/batch result carries answered_by — model when the classifier answered, keyword when the keyword scan produced the band, none when neither did — so no reader infers it from the shape. A context_fit the classifier scores at exactly 0.0 is served as 0.0; its score was served as null
v2.0.0September 2026
  • Observation topic label (collection days from September 23, 2026): paid observations and their signed receipts name the prompt set consumer-brand-watch at prompt.topic_ref and in the receipt meta.topic. Observations collected September 14 to 22, 2026 carry the topic reference W1 Neutral Scope - X116 (S116/D022), the internal name of the same prompt set; topic= on GET /v1/observations accepts either value and returns one series. Signed receipts are never rewritten
  • The cosigner bar published (September 12, 2026): /docs/cosigner-bar — what BlueFox Edge requires of an independent cosigner of its transparency log: machine-checked tests, a declaration in the cosigner's own words, and the limits stated beside each one
  • bluefox-edge 0.0.1 published to npm and PyPI (September 12, 2026): the offline receipt checker as an installable package under the SDK's name — the API client the SDK pages document arrives at 0.6+
  • bluefox-verify-receipt 0.0.1 published to PyPI (September 12, 2026): the served Python checker, pip-installable — the exact published bytes, one command, no client, no account
  • @bluefoxedge/verify-receipt 0.0.1 published to npm (September 12, 2026): the scoped twin of bluefox-verify-receipt 1.1.0 — the same single-file checker under the @bluefoxedge namespace
v2.0.0August 2026
  • Checkpoint anchoring shipped end-to-end (August 2026): transparency-log checkpoint roots are committed into the Bitcoin chain and served with their proofs at GET /v1/transparency/anchor. The matching keyless checker, verify_anchor.py (published August 27, 2026 at api.bluefoxedge.ai/verify_anchor.py, checksum beside it), fetches no key set and checks no signature of ours — it asks the Bitcoin chain, through public APIs nobody here operates, whether the root you name is committed and how deep
  • Payments index (August 24, 2026): GET /v1/transparency/payments — how many log entries bind one settlement transaction, answered as a count plus a membership assertion, never a list; fenced to callers who present the transaction hash beside a receipt-derived key
  • Checkpoint history (August 23, 2026): GET /v1/transparency/checkpoints/history — the signed checkpoint sizes this log actually published, newest first, so a verifier can ask for a checkpoint that exists instead of sweeping integers
  • JavaScript receipt verifier published to npm (August 21, 2026): bluefox-verify-receipt 1.1.0 — run npx bluefox-verify-receipt your-receipt.json with nothing installed; the package ships the same single file as the served verify_receipt.js and takes the same --jwks flag for fully offline runs
  • Programmatic key door (August 20, 2026): POST /v1/api-keys/programmatic — the machine-to-machine twin of the browser signup: same free tier, same terms, no browser and no bot challenge; a program obtains a key unattended in one request, capped per caller and across the endpoint, idempotent on retries
  • Evidence bundle format 1.2 (August 3, 2026): exported bundles gain an optional transparency member and per-receipt inclusion sidecars — a bundle can now carry the proof that its receipts are in the log, and the format string on every bundle names the shape it uses
  • Version of record: the API's identity surfaces — openapi.json, llms.txt, capabilities.json, and the MCP server card — now state one version, 2.0.0
  • Endpoint reference filled in: every operation in openapi.json carries a written summary and description
v2.0.0-rc2August 2026RC
  • Payment-rail interop fix (August 12, 2026): 402 quotes now speak the x402 v1 network dialect (base) and the payment path verifies and settles both protocol dialects — the first build a stock x402 client library can pay end-to-end (the prior CAIP-2-labeled quote was not payable by standard clients)
  • x402 payments moved from the Base Sepolia testnet to Base mainnet (eip155:8453) — USDC, pay per call, no API key required
  • New endpoint: POST /v1/notarize/hash — notarize a client-presented digest as a signed receipt; no API key required (x402-payable per call), signed in-request
  • Receipt signing live in production — signed reliance receipts, published key set at /.well-known/jwks.json, public specimen pair with the offline check on the learn page
  • Health alerting for sustained model-fallback engagement
v2.0.0-rc1April 2026RC
  • Plugin architecture for verification domains — add new domains without core changes
  • 6 Edge Ops feed compilers: Security, Commerce, Model, Protocol, Trust, Regulatory
  • Remote MCP transport via Streamable HTTP at /mcp
  • 26 MCP tools
  • x402 payment support — USDC on the Base Sepolia testnet (eip155:84532), $0.001 per lookup (superseded August 2026: payments moved to Base mainnet — see v2.0.0 above; kept here as dated history)
v1.5.0March 2026
  • All 9 verification domains live: Brand, Compliance, Price, Policy, Financial, Freshness, Competitive, Spec, Package
  • 1,000 brands with structured reference data
  • Citation verification endpoint
  • MCP Scanner — 75+ servers scanned across 6 behavioral dimensions
v1.0.0March 2026
  • Initial API launch
  • Brand verification with ground truth reference data
  • Policy verification for return policies and warranties
  • API key authentication and free tier (100 calls/day)
  • MCP server with 15 initial tools