>_ what gets listed

// not everything with an API belongs here. but it's not just APIs either.

We list anything a bot can use without a human in the loop.

Here's what qualifies.

$ required

One thing. Your service, tool, or resource must have a machine-readable interface a bot can use.

That could be:

APIREST, GraphQL, or any callable endpoint

MCP Serverstandardized agent tool access

Skill File.md / .json / .yaml instructions agents can consume

Plugin Manifestai-plugin.json or equivalent

llms.txtLLM-readable context file

Structured FeedJSON feed, RSS, or machine-readable data

Agent ProtocolA2A, ACP, UCP, or other agent-to-agent endpoint

If the only way to use it is through a browser with human eyes, it doesn't belong here.

$ what agents filter by

Services self-report these features. They show as badges on your listing. Agents use them to filter the directory.

REST APIreturns structured data (JSON, GraphQL, protobuf)

MCP Serverpublished MCP server for zero-integration access

OpenAPI Specmachine-readable API specification

Skill Fileagent-consumable instructions or tool definitions

Plugin Manifestai-plugin.json or equivalent discovery file

llms.txtLLM-readable site context

Accepts MPPTempo MPP machine payments

Accepts x402HTTP-native stablecoin payments

Supports ACPAgentic Commerce Protocol

Supports UCPUniversal Commerce Protocol

Webhooksasync event notifications

Free Tierfree tier or trial available

Bot-Friendly ToSterms explicitly allow automated access

$ what doesn't belong

[✗]No machine-readable interface (browser-only, human-only)
[✗]Spam or duplicate submissions

// self-reported. badges are the signal.

>_ ready to list?

Submit your service. It goes live instantly.

The more agent features you support, the more badges your listing shows.

submit your service

>_

Not everything with an API belongs here. But it's not just APIs either.