BlueFox Edge

The reference layer agents route through.

~150 tokens per call. ~400ms typical (fast path). ~30× cheaper than web-search-and-parse.
1000+ brands. 9 verification domains — 1 validated (financial), 8 not-yet-validated.

Response time varies by verification depth — the figure above is the typical fast-path read; deeper LLM-backed checks take longer. Cost-ratio basis: the token-economics methodology in capabilities.json.

Free tier: 100 API calls per UTC day · 1 signed mint per UTC day, no card required.
Two meters, one bill: your plan sets the API-call allowance (100 requests/day on the free tier), while signed mints are counted separately — only the free tier is mint-capped, at 1 signed mint per UTC day. A mint spends one call from that same allowance, so the mint cap sits inside it, not beside it, and a third ceiling sits inside the same allowance: 10 claim-verification calls per UTC day. Paid plans include signed mints — your plan's daily call limit is the only meter. Every keyless call has a posted per-request price — the x402 table at /.well-known/x402 is the whole keyless price list, and each door's 402 is the quote of record. With a key, calls draw on your plan; the mint is the only act the free tier meters separately.
A key is for making calls and minting receipts — checking a receipt never needs one: verification runs offline against the published key set.
No account at all? Priced endpoints also accept x402 per-request payment (USDC) — send the request without a key and the HTTP 402 response quotes the exact terms. POST /v1/notarize/hash works fully keyless; the machine-readable listing is at /.well-known/x402.
Every verification mints a signed receipt — fetch the published sample at www.bluefoxedge.ai/specimen-receipt.json and check it yourself with the runnable verifier at /getting-started (step 4): offline, no key required.
Docs: /docs · Capabilities: /capabilities.json