api reference
Check & verify
Score any site for bot-friendliness, and probe a service's claimed interfaces.
POST/api/v1/verify
Check whether a service really exposes the interfaces it claims. Each endpoint you name is fetched and inspected, and the verdicts come back. Nothing is written and no auth is required — this is the same probe that runs on submissions, owner updates and discovery, exposed so an external workflow doesn't have to reimplement it and drift. Returns listable (did anything check out), verified (the flags that passed) and a probe result per claim. Rate limited to 60 calls/hour per IP.
parameters
url (required)the service's own URLhas_mcp_server, mcp_server_urlMCP server to probehas_openapi_spec, openapi_spec_urlOpenAPI spec to probehas_skill_file, skill_file_urlskill file to probehas_llms_txt, llms_txt_urlllms.txt to probehas_structured_feed, structured_feed_urlstructured feed to probe
example
curl -X POST "https://www.botfriendly.xyz/api/v1/verify" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","has_mcp_server":true,"mcp_server_url":"https://example.com/mcp"}'GET/api/v1/check
Score how bot-friendly a site is. Fetches it the way an agent would (no JavaScript) and reports access, no-JS content, and machine discovery out of 100, with advice per failed check. Rate limited to 6 checks/min per IP.
parameters
url (required)site to check (scheme optional, https assumed)formatprompt returns a ready-to-paste coding-agent prompt covering every failed check, instead of the JSON report
example
curl "https://www.botfriendly.xyz/api/v1/check?url=yourservice.dev"