Submit a service

Give us the address of a paid API endpoint, a remote MCP server or an A2A agent card, and we start checking it, the same way we check services we read from registries.

What happens next

• We make one unpaid request soon, usually within the hour, then on the usual schedule. We never pay, never call an MCP tool and never send an agent a task.
• The service is in our index straight away, with its page and check history. It joins the directory when its checks meet our listing criteria, and a small AI model places it in the tree from what the service itself says.
• We take only the address. A name or description from the sender is never published; the service is named by its host until its own answers say more.
• A paid endpoint passes when it answers with a valid payment request on a production network (x402, MPP or L402). Sending us a website's home page won't list it: we list services agents call.

Agents can do the same with POST /api/v1/submissions and JSON {"url": "https://..."} (optional kind and method), or the MCP tool submit_service. No key needed; at most 20 a day per address. To enforce the limit we keep a one-way hash of your address together with the date, which cannot be linked across days. Run a host and don't want it checked? Use the opt-out page.