Remote service terms and limitations#

The remote MCP is an optional, best-effort public interface to the open-source resolver. The code's MIT license includes its existing warranty disclaimer. There is no availability SLA.

The public budget is shared: at most 100,000 gateway HTTP admissions per UTC day. Protocol setup, invalid requests and burst rejections spend this budget too. After exhaustion, requests return HTTP 429 until midnight UTC. Counter failures stop execution. Network and provider failures can also make tools unavailable. Cloudflare can bill rejected ingress; the public ceiling controls admission to the resolver, rather than the platform's total billable network traffic.

Use the published tool bounds. Do not use this endpoint for corpus-scale batches, unrestricted graph crawling, arbitrary SPARQL or provider quota circumvention. The local CLI and JSONL workflows are the appropriate corpus-scale interface.

Wikidata evidence is provided under Wikidata's data licensing. Provider concordance does not prove your local entity's identity. A returned sameAs candidate requires independent review before publication. Preserve HOLD, AMBIGUOUS, insufficient evidence and wrong-identity results.

Read remote data handling before sending requests. The endpoint does not require secrets and does not support Google KG remotely. Product support is available through project issues.