Skip to content

BY THE APIDECK TEAM

One registry for developers and agents.

Developers need to understand an integration. Agents need to use it. Both depend on clear capabilities, the right permissions and requests that work.

Different interfaces. A shared foundation.

Developer experience (DX) covers how people build and debug integrations. Agent experience (AX) covers how agents discover and use capabilities within the permissions their host provides.

Discover

FOR DEVELOPERS

Read documentation, compare APIs and find SDKs.

FOR AGENTS

Discover tools through descriptions and parameter schemas.

Connect

FOR DEVELOPERS

Understand account setup, credentials and permissions.

FOR AGENTS

Follow the server’s setup instructions. HTTP authorization and local package credentials depend on server and client support.

Execute

FOR DEVELOPERS

Explore requests, inspect responses and debug errors.

FOR AGENTS

Call tools with structured inputs and inspect their results.

Evaluate

FOR DEVELOPERS

Check publisher sources, review dates and test evidence.

FOR AGENTS

Use the same evidence to inform which connections the host permits.

Know what a listing actually tells you.

Publisher affiliation, documentation review and a successful test answer different questions. No single badge covers them all.

Who publishes it?

Official describes publisher affiliation. It does not mean every tool has been tested or security assessed.

How Official status works →

What supports the claim?

Check the linked documentation and its review date. A source check applies to the stated fact, not every capability.

Read our evidence definitions →

What was tested?

A connection check, tool discovery and a successful tool call are separate results. Look for the scope and date.

Understand testing limits →

WHERE WE’RE HEADING

Toward an autonomous registry.

Discover continuously. Verify with evidence. Publish with control.

We’re building toward a registry that finds new integrations, checks sources, catches duplicates and keeps records current. Automation should handle repeatable work, with review where judgment matters.

Today, source aggregation and submission handoff support that process. The complete research, publication and notification loop is still being developed. A submitted or approved entry is not proof that it is live, official or tested.

Search API Tracker

Curated starting points