hosted lanes
The optional hosted lanes.
WhiteMagic runs locally by default and needs no service from us. These lanes exist for evaluation and for teams that want a checkable endpoint – read-only, rate-capped, and honest about their limits.
Recall – read-only
A hosted MCP endpoint at mcp.whitemagic.dev/mcp (streamable-http) serves recall over a curated public corpus: docs, spec, release notes, and the grimoire. Keyless initialize / tools/list for directory probes; free evaluation keys are instant at mcp.whitemagic.dev/keys (no account, daily-capped). Your local store is never uploaded.
Verify, anchors, receipts
A stateless verification API at api.whitemagic.dev: keyless /health, /info, and /openapi.json; keyed /verify (bundle → verdict, optional signed verification receipt), /verify-receipt, /verify-anchor, and /anchors (OpenTimestamps proof hosting; keyless fetch at /anchors/<digest>). The format and the five-minute walkthrough are on the trust and receipts pages.
Evaluation endpoint
Add / Search / Delete over a participant-isolated store for evaluation harnesses: api.whitemagic.dev/eval (keyless health at /eval/health; access token on request; eval-only infrastructure, no SLA).
Metering and keys
Metered calls settle per call in USDC on Base via x402: a keyless call to a keyed method answers HTTP 402 with the payment requirements in the challenge – no account, no invoice. Free evaluation keys stay free; per-contract keys carry higher caps and metered audit lines. For scopes and terms, see work with the lab or contact.
What is recorded, and the limits
The gateways record one access entry per request – key name, timestamp, method, status, and response size – never bundle contents, IP addresses, or query text. Bundle verification is stateless: content is checked in memory and dropped. Details in the Privacy Policy and Terms. The lanes are read-only, rate-capped, carry no SLA, and run under partial kernel confinement – disclosed, not hidden.