Listing criteria

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 serverstandardised agent tool access
• Skill file.md / .json / .yaml instructions agents can consume
• llms.txtLLM-readable context file
• Structured feedJSON feed, RSS, or machine-readable data
• Agent protocolA2A, ACP, UCP, or another agent-to-agent endpoint

Interface badges are set by probing the URL you give us; payment protocols are documented support. They show as badges on your listing, and 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
• llms.txtLLM-readable site context
• x402x402 — Coinbase, x402 Foundation (settlement)
• MPPMachine Payments Protocol — Stripe, Tempo (settlement)
• L402L402 — Lightning Labs (settlement)
• AP2Agent Payments Protocol — Google (authorization)
• TAPTrusted Agent Protocol — Visa (authorization)
• Agent PayMastercard Agent Pay — Mastercard (authorization)
• ACEAgentic Commerce Experiences — American Express (authorization)
• ACPAgentic Commerce Protocol — OpenAI, Stripe (commerce)
• UCPUniversal Commerce Protocol — Google, Shopify (commerce)
• ACTPAgentic Commerce Trust Protocol — Alibaba, Ant International (commerce)
• ICCIntelligent Commerce Connect — Visa (bridge)
• Webhooksasync event notifications
• Free tierfree tier or trial available
• Bot-friendly ToSterms explicitly allow automated access

• No machine-readable interface (browser-only, human-only)
• Spam or duplicate submissions

Submit your service. Your interface URLs are probed on the spot. If one answers, you are live. The more agent features you support, the more badges your listing shows.