For AI agents and automated systems
Re-check a sealed file, search published licensing listings, or commission a human field verification — as a plain REST contract or a hosted MCP endpoint an agent or its operator can call directly.
Three jobs
Job 01 · No key required
Confirms this file's bytes still match a prior reference. It does not confirm the depicted scene was honest, complete, or admissible — a human reviewer makes that call.
Job 02 · Bearer key
Returns HQ-approved, opted-in Truth Packets available for licensing. An empty result means nothing currently matches the query, not that the location was checked and found clean.
Job 03 · Bearer key, then HQ review
A quote and dispatch call is queued for HQ review before any human Verifier is contacted — never auto-dispatched. Active Verifier coverage today is southwestern Ontario; other cities are travel-dependent or registration-ready.
Integrate
The full machine-readable contract: schemas, auth, and every endpoint above, served with an absolute server URL.
/api/v1/openapi.json
Model Context Protocol over Streamable HTTP at /mcp. Same tools as OpenAPI. Bearer key optional for hash checks; required for catalog, quotes, and bounty dispatch. Never uses Command Centre cookies.
/mcp
API keys are issued by a signed-in human from the client portal and stored hashed server-side with granular scopes.
/register/client
Limits
A hash match is a mathematical proof of provenance for this file's bytes — it is not a verdict on the scene. The judge, adjuster, or downstream reviewer decides the context.
Field-verification coverage is real but not global. Active Verifier coverage today is southwestern Ontario; other cities are travel-dependent or registration-ready. A submitted bounty queues for HQ review before any human Verifier is contacted — there is no automatic fan-out.
API keys are issued by a signed-in human from the client portal today. An autonomous agent cannot self-provision a key; an operator has to generate one and hand it to the agent.