Developers

Catalog API, early access

Status

The Catalog API is in early access and is not live yet. There is no callable endpoint and no API key to use today. This page describes what the API will return and how to request a place, so builders can plan against the record shape instead of scraping pages.

What the API will return

The same records the public catalog publishes, as structured data: tools, MCP servers, frameworks, categories, curated stacks, and sourced compatibility records. Each record carries its verification state and check date, its setup paths and placeholder configuration where the profile has them, and pricing and license summaries as sourced facts or as unknown. Nothing enters the API that has not passed the publication gate on the methodology page.

Change records are part of the planned surface: new versions, pricing changes, and listings going stale, for the entries a builder watches. That is the data behind the change alerts described on the pricing page.

Record shape, preview

The block below is a preview of the planned record shape. Field names and values are illustrative, marked with placeholders, and nothing here is a live response.

Catalog API record preview (planned, not a live response)

{
  "id": "tool:<slug>",
  "object": "catalog.tool",
  "name": "<verified display name>",
  "profile_url": "https://agentsuse.com/tools/<slug>",
  "summary": "<one-sentence pitch from the published profile>",
  "category": "<primary category>",
  "verification": {
    "status": "source_verified",
    "checked_at": "<YYYY-MM-DD>"
  },
  "pricing": {
    "model": "<sourced model, or unknown>",
    "summary": "<sourced pricing summary, or unknown>"
  },
  "sources": ["<official site>", "<official docs>", "<registry or repo>"]
}

Planned endpoints

Endpoint paths are planned, not callable. They are published so early access conversations can be concrete about scope.

Planned Catalog API endpoints and what each will return. None of these endpoints is live yet.
Method	Planned path	Returns	Status
`GET`	`/v1/tools`	Published tool records with verification state and check dates	Planned
`GET`	`/v1/tools/{slug}`	One tool record, including setup paths, limits, and sourced relationships	Planned
`GET`	`/v1/mcp-servers`	Published MCP server records with transport, runtime, and config notes	Planned
`GET`	`/v1/frameworks`	Published framework records with sourced tool compatibility	Planned
`GET`	`/v1/changes`	Change records for watched entries: versions, pricing changes, stale listings	Planned

Licensing posture

This preview grants no license and no access. Early access terms will be stated before any key is issued, covering permitted use, attribution, caching, and redistribution, and the terms of use continue to govern the public website. One rule is already fixed and will not move: API access never changes a listing, a ranking, or a conclusion in the catalog.

Request early access

Use the contact page and mention the Catalog API. Say what you are building, which records you need (tools, MCP servers, frameworks, compatibility, changes), and which runtime your agents run on. Early access places open as the API does; there is no key to send before then.

Until the API opens, the browser workspace is the working surface: saved stacks with JSON and CSV export and a watchlist, described on the pricing page. The roadmap shows where the API sits in the product sequence.