Trustbase Lab · MCP Access
Our MCP data service is open to everyone: no sign-up, no key, free access to every published tool. An API key is an optional upgrade — and its only reason to exist: when a record is corrected, withdrawn or re-graded, we can find you and tell you. Still free, same data, same 59 tools.
中文 · MCP access docs · Usage board · Methodology
The tiers are functionally identical — a key unlocks no extra tools or data. What it buys is correction notices: when a record goes wrong we can reach you. It also switches attribution to per-key and lifts the anonymous rate limit.
| Anonymous (default) | Keyed (optional) | |
|---|---|---|
| Cost | Free | Free (this release) |
| Correction notices | None — anonymous calls are unattributable, so we cannot tell you | Proactive email notice when a record you called in the last 180 days is corrected / withdrawn / re-graded / its source link dies |
| Requires | Nothing — call the endpoint right away | Email application, issued manually |
| Rate limit | 120 requests per minute per IP (burst protection) | Anonymous limit not applied |
| When limited | 429 + Retry-After, never a ban; works again once the window resets | — |
| Attribution | Salted hash (not reversible) | Per key (more accurate; shown on the usage board) |
| Tools | All published tools | All published tools |
Data will go wrong — the real question is not “whether”, but “who tells you when it does”. With anonymous calls we don’t know who you are, so we cannot notify you. With a key, we can. That promise is the only reason the key exists — and it is how “freedom from error” stops being a slogan and becomes a mechanism.
business@trustbaselab.com and include: your use case (which kind of agent / application, which tools you plan to call); your organisation (optional); an rough expected call volume; and a notification address (required — used for correction notices only, never for marketing). Keys are issued manually after review. The full key appears exactly once in the issuance email — store it safely. We only keep a sha256 digest of the key (first 16 hex chars) and cannot recover the original; ask us to revoke and re-issue if it is lost or possibly leaked.Either standard header works with any MCP client:
Authorization: Bearer <your-key>X-API-Key: <your-key>X-Trustbase-Auth: anon (key_invalid). That header means the key is broken (mistyped or revoked); check it and retry. Rationale: a 401 would turn callers away, while anonymous fallback keeps the service uninterrupted and still makes the failure discoverable.The anonymous tier uses a sliding window (120 requests/min/IP). It is burst protection, not a quota: exceeding it returns 429 with a Retry-After header and instructions for requesting a key. No bans — once the window resets you can continue, or apply for a key to lift the constraint.
Metering follows exactly the same rules as the usage board: call metadata only (tool name, time, salted hash, success flag) — never the body of your queries. Free does not mean unmetered: the record itself is our public answer to who uses the service and how much. Terms: /terms · privacy: /privacy. The email tied to an API key is used for correction notices only — never for marketing, never shared.
Trustbase Lab · independent third-party industry data infrastructure ｜ MCP endpoint: /ai ｜ usage board: /en/usage/ ｜ methodology: /en/methodology/