Kept Current Automatically
The price and tool-name table cells on this site are now produced by a generator that reads the LimitGuard API’s own source instead of transcribing it by hand. This entry is the first such render, run by hand. Once the sync workflow lands, a pull request will open against this repository whenever a price or an MCP tool name changes there, with the affected cells already updated. Until then these pages stay hand-maintained.The September 5 corrections were found by reading the docs
against the live API by hand. The generator is meant to make that sweep unnecessary for
the values it covers — the prices and the MCP tool names in the tables listed below.
MCP tool names corrected
Pricing paired two of the five REST mirror paths with tool names the MCP server does not answer to:
The sample
/.well-known/mcp.json response in
AI agent integration named the
same two tools the same wrong way. It now matches what that endpoint returns.
The names only matter over the MCP transport — tools/call with the old name returns
Unknown tool. The REST paths themselves are unchanged, so nothing calling
/v1/mcp/trust-score over plain HTTP was affected.
The September 5 entry lists the five tools with the same two
mistakes in it. It is left as written: a changelog records what was said on a date, and
these pages are now generated with that directory excluded for exactly that reason.
What is generated
Prose is not generated, and neither are the JSON samples — the
/.well-known/mcp.json
sample corrected above is a hand fix, and tool names quoted outside a table stay
hand-maintained. Only the table cells that quote a number or a tool name are generated,
so an endpoint that gains a price but no row here is reported rather than invented — the
sync says so instead of writing a description nobody wrote.