Skip to content

HomeGitHub

AliveRegistry

Autopia

io.github.MaydayTrey/autopia

Verified, reproduced behavior of public HTTP APIs: spec gaps, errors, pagination, auth.

This endpoint completed initialize and tools/list. No tool was called.

Rank
#3124
Score
81
Tool tokens
1,797
Tools
9

Tools

Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.

  • list_tools

    The APIs the compendium covers: each with the hosts its trials hit, trust tier, version count, and counts of verified claims and spec divergences.

  • list_versions

    The spec versions recorded for one API, newest first, each fingerprinted by its spec hash. The ids identify versions for get_version_diff.

  • get_tool_knowledge

    Every verified claim about an API as structured records (latest version by default): paginated, filterable by kind, spec divergences flagged, each with compact evidence (trial id, probe, status, reque

  • get_divergences

    Where the live API contradicts its own OpenAPI spec: documented limits not enforced, types not validated, required parameters not required, enums accepting other values. Compact evidence; verbose=true

  • search_claims

    Full-text search over verified claims by host and symptom, e.g. "github per_page 500", "npm search size 0", "is latitude required on /v1/forecast": the lookup for an unexpected 4xx/5xx, a parameter th

  • get_tool_docs

    The verified behavior sheet for an API: Markdown built only from verified claims, with spec contradictions first, then sibling differences, undocumented rules, and per-endpoint behavior (error shapes,

  • get_version_diff

    What changed in verified behavior between two spec versions of an API (changed, added and removed claims), as opposed to what changed in the spec text.

  • request_target

    Queues a public, read-only, credential-free API for probing, from a target object { name, spec_url (OpenAPI 3 document), category?, include_paths?, baseline? (valid values for required params per path

  • get_request_status

    Status of a target request (pending, running, done or failed), with the run id and summary once processed.

Nearby in GitHub

#1
Context7

Up-to-date code docs for any prompt

Alive
score
95
#4
SerpApi

Official SerpApi MCP server for Google, Bing, and other search engines.

Alive
score
94
#5
pg-aiguide

Comprehensive PostgreSQL documentation and best practices, including ecosystem tools

Alive
score
92