Submissions

POST/api/v1/submissions

Submit a new service. No auth required. Needs an MCP server, OpenAPI spec or live API (has_mcp_server, has_openapi_spec or has_api) on the service's own domain or linked from it; interface URLs are fetched during the request and the listing publishes immediately if one of those completes a handshake, or returns 422 with the probe results and an error code if not. llms.txt, skill files and feeds add badges but don't qualify a listing alone. Article URLs (/blog/, /news/, dated paths) are rejected, and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon: send icon_url or icon_base64, or leave both out and the service's own site is checked for one.

parameters

• name (required)service name
• url (required)service URL
• category (required)category id from /categories
• description (required)max 120 chars
• auth_methodapi-key, m2m-oauth, bot-token, wallet, x402-none, none
• has_mcp_server, mcp_server_urlMCP server support
• has_openapi_spec, openapi_spec_urlOpenAPI spec support
• has_api, api_urllive API base (api.example.com, or under /api or /v1)
• accepts_mpp, accepts_x402payment protocol support
• has_skill_file, has_llms_txtintegration files
• billing_modelpay-per-request, subscription, free, etc.
• has_free_tierboolean
• tagsarray of strings
• contact_emailfor verification

example

curl -X POST "https://botfriendly.xyz/api/v1/submissions" \
  -H "Content-Type: application/json" \
  -d '{"name":"YourService","url":"https://example.com","category":"browse","description":"What it does"}'