Agent sign-up check

Can an agent sign up here?

Seven checks for whether an AI agent can sign up for a developer platform, pay for it and use it on its own. Each one reads what the platform publishes, with plain GET requests, and cites the spec it checks against. Run them on any domain, or read the results for 100 platforms below.

None of the 100 platforms passes all seven. See the results

100 platforms,
November 12, 2026.

Ranked by checks passed. Ties share a rank and are listed by name. Pick a platform for the reason behind each mark.

0of 100 pass all seven checks
6/7the best score, Telnyx alone
0of 100 publish a spend cap in a machine-readable form
5/7Prized, on the same script: fails spend limits and only partly passes payment handoff

None passes all seven. The highest score is 6 of 7 (Telnyx). 0 of 100 publish a spend cap in a machine-readable form the check accepts (the draft Prized wrote, or the AAuth budgets Internet-Draft, an individual submission); 6 more only mention limits or budgets in their docs. No platform passes that check, so none can pass all seven. 2 of 100 publish a machine-readable way for an agent to pay. 20 of 95 APIs answer a signed-out call with a challenge an agent can parse (a 401 with WWW-Authenticate, or a 402 payment requirement); most send a 401 with no WWW-Authenticate header. 8 checks on 3 platforms could not be read on the day of the run (the file gave no answer: a bot wall, a server error, a 429, a failed connection, or the script’s own request cap); they are shown as not read, not as fails. Prized scores 5 of 7 on the same script, tied with 3 others for rank 2 of 100. It fails spend limits and only partly passes payment handoff.

Pass
Partly
Fail
Not run, or not read

Every reason, quote and request (JSON)

100 platforms ranked by checks passed, November 12, 2026
Rank	Platform	Score	1auth.md	2Metadata	3Sign-up API	4401 challenge	5Spend limits	6Payment	7Markdown
1	Telnyx, show the reasons Email, phone and messaging	6/7	pass	pass	pass	pass	fail	pass	pass
1. auth.md, pass. auth.md documents agent registration (https://api.telnyx.com/v2/bot_signup) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (service_auth, anonymous) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, pass. Publishes an x402 discovery document (/.well-known/x402) that an agent can pay from without an account 7. Docs in Markdown, pass. llms.txt found
2	Firecrawl, show the reasons Browsers and scraping	5/7	pass	pass	pass	pass	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://www.firecrawl.dev/agent/auth) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (identity_assertion) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
2	Kernel, show the reasons Browsers and scraping	5/7	pass	pass	pass	pass	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://api.onkernel.com/authmd/agent/auth) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (identity_assertion) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
2	Polar, show the reasons Payments and billing	5/7	pass	pass	pass	pass	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://api.polar.sh/v1/agent/identity) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (anonymous) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
2	Prized, show the reasons Sandboxes and compute	5/7 +1 partly	pass	pass	pass	pass	fail	partly	pass
1. auth.md, pass. auth.md documents agent registration (https://api.prized.dev/api/v1/agent/identity) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (service_auth, identity_assertion) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. auth.md mentions a payment path (billing_url) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
6	Boat, show the reasons Sandboxes and compute	4/7 +2 partly	pass	partly	pass	pass	fail	partly	pass
1. auth.md, pass. auth.md documents agent registration (/api/boat/agent/identity) 2. Protected resource metadata, partly. resource (https://boat.dev/api/box/v1/) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, pass. agent_auth names a registration endpoint (anonymous, service_auth) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. auth.md mentions a payment path (billing_required) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
6	Bright Data, show the reasons Browsers and scraping	4/7 +1 partly	pass	pass	pass	partly	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://brightdata.com/users/auth/agent_registration/auth) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (identity_assertion) 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
6	Neon, show the reasons Databases and backend	4/7 +1 partly	partly	pass	pass	pass	fail	fail	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# Claimable Neon) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, pass. agent_auth names a registration endpoint (anonymous) 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	AgentMail, show the reasons Email, phone and messaging	3/7 +2 partly	pass	partly	partly	pass	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://api.agentmail.to/v0/agent/sign-up) 2. Protected resource metadata, partly. Metadata names no authorization_servers, so an agent cannot find where to register 3. Sign-up by API, partly. auth.md documents a sign-up API (https://api.agentmail.to/v0/agent/sign-up), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	Autumn, show the reasons Payments and billing	3/7 +2 partly	pass	pass	partly	partly	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://api.useautumn.com/agent.provision) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, partly. auth.md documents a sign-up API (https://api.useautumn.com/agent.provision), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	Cloudinary, show the reasons Dev tools	3/7 +1 partly	pass	fail	partly	pass	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://api.cloudinary.com/v1_1/provisioning/clouds) 2. Protected resource metadata, fail. Protected resource metadata answers HTTP 403 3. Sign-up by API, partly. auth.md documents a sign-up API (https://api.cloudinary.com/v1_1/provisioning/clouds), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, pass. 401 with a Basic challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	Context.dev, show the reasons Search and data	3/7 +2 partly	pass	partly	pass	partly	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (https://www.context.dev/agent/identity) 2. Protected resource metadata, partly. resource (https://api.context.dev/) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, pass. agent_auth names a registration endpoint (service_auth) 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	Financial Datasets, show the reasons Search and data	3/7 +1 partly	fail	fail	partly	pass	fail	pass	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.financialdatasets.ai/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.financialdatasets.ai/.well-known/oauth-protected-resource) 3. Sign-up by API, partly. llms.txt documents a sign-up API (/agent/signup), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, pass. 402 Payment Required: the API takes payment from a client with no account 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, pass. The API answers 402 with an x402 payment requirement 7. Docs in Markdown, pass. llms.txt found
9	PostHog, show the reasons Dev tools	3/7 +2 partly	partly	pass	partly	pass	fail	fail	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# PostHog) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, partly. agent_auth names the OAuth token endpoint (https://us.posthog.com/oauth/token/) as its identity endpoint: it exchanges an assertion for a token, it does not register a new account 4. Key works without a browser, pass. 401 with a Bearer challenge that points to resource metadata (RFC 9728 section 5.1) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	Sentry, show the reasons Dev tools	3/7	fail	pass	fail	pass	fail	fail	pass
1. auth.md, fail. The site answers any path with the same Markdown page, so this is not an auth.md 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Bearer challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
9	WorkOS, show the reasons Dev tools	3/7 +1 partly	pass	fail	pass	partly	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (/x/one-shot-environments) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, pass. agent_auth names a registration endpoint (service_auth) 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Beam, show the reasons Sandboxes and compute	2/7	fail	fail	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.beam.cloud/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.beam.cloud/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Bearer challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Browserless, show the reasons Browsers and scraping	2/7 +1 partly	fail	pass	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.browserless.io/auth.md) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Clerk, show the reasons Dev tools	2/7 +3 partly	pass	partly	partly	partly	fail	fail	pass
1. auth.md, pass. auth.md documents agent registration (/v1/accountless_applications) 2. Protected resource metadata, partly. Metadata names no authorization_servers, so an agent cannot find where to register 3. Sign-up by API, partly. auth.md documents a sign-up API (/v1/accountless_applications), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Exa, show the reasons Search and data	2/7 +3 partly	partly	pass	fail	partly	fail	partly	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. auth.md mentions a payment path (`402`) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
17	Fly.io, show the reasons Sandboxes and compute	2/7 +2 partly	partly	partly	fail	pass	fail	fail	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, partly. resource (https://mcp.fly.io) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Basic challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Hugging Face, show the reasons LLM APIs	2/7 +1 partly	fail	partly	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, partly. resource (https://huggingface.co/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Bearer challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
17	Loops, show the reasons Email, phone and messaging	2/7 +2 partly	partly	pass	fail	partly	fail	fail	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Mailgun, show the reasons Email, phone and messaging	2/7 +1 partly	fail	partly	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.mailgun.com/auth.md) 2. Protected resource metadata, partly. resource (https://www.mailgun.com/wp-json/mcp/mcp-oauth-server) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Basic challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
17	MongoDB Atlas, show the reasons Databases and backend	2/7	fail	fail	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.mongodb.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.mongodb.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.mongodb.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Digest challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	OpenAI, show the reasons LLM APIs	2/7	fail	fail	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Bearer challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
17	Perplexity, 1 not read, show the reasons LLM APIs	2/7 +1 partly 1 not read	not read	pass	fail	partly	fail	fail	pass
1. auth.md, not read. Not read on 2026-11-12: https://perplexity.ai/auth.md answered with a Cloudflare bot challenge 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt (not read on 2026-11-12: https://perplexity.ai/auth.md answered with a Cloudflare bot challenge) 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt (not read on 2026-11-12: https://perplexity.ai/auth.md answered with a Cloudflare bot challenge) 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt (not read on 2026-11-12: https://perplexity.ai/auth.md answered with a Cloudflare bot challenge) 7. Docs in Markdown, pass. llms.txt found at a docs path
17	PlanetScale, show the reasons Databases and backend	2/7 +1 partly	fail	pass	fail	partly	fail	fail	pass
1. auth.md, fail. A Markdown page is served at /auth.md, but it is not about agent sign-in (it never mentions auth.md, agent_auth, or how an agent gets a credential) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Railway, show the reasons Sandboxes and compute	2/6 +1 partly	partly	pass	fail	not run	fail	fail	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# Authenticating to Railway) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, not run. GraphQL API that takes queries by POST only; this checker sends GET requests only 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Resend, show the reasons Email, phone and messaging	2/7 +2 partly	partly	pass	fail	partly	fail	fail	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Supabase, show the reasons Databases and backend	2/7 +1 partly	fail	pass	fail	partly	fail	fail	pass
1. auth.md, fail. A Markdown page is served at /auth.md, but it is not about agent sign-in (it never mentions auth.md, agent_auth, or how an agent gets a credential) 2. Protected resource metadata, pass. Names 1 authorization server 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
17	Twilio, show the reasons Email, phone and messaging	2/7	fail	fail	fail	pass	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.twilio.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.twilio.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.twilio.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Basic challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	AgentPhone, show the reasons Email, phone and messaging	1/7 +2 partly	fail	fail	partly	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://agentphone.ai/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://agentphone.ai/.well-known/oauth-protected-resource) 3. Sign-up by API, partly. llms.txt documents a sign-up API (/v0/agent/sign-up), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Anthropic, show the reasons LLM APIs	1/7 +2 partly	fail	fail	fail	partly	partly	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.anthropic.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.anthropic.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.anthropic.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, partly. llms.txt mentions spend limits in prose; no machine-readable cap 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Apify, show the reasons Browsers and scraping	1/7 +5 partly	partly	partly	fail	partly	partly	partly	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, partly. resource (https://mcp.apify.com) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, partly. auth.md mentions spend-capped in prose; no machine-readable cap 6. Payment handoff, partly. auth.md mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	AssemblyAI, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.assemblyai.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.assemblyai.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.assemblyai.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	AWS, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://aws.amazon.com/auth.md/) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. HTTP 400 asking for a key, instead of a 401 challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Blaxel, show the reasons Sandboxes and compute	1/7 +3 partly	partly	partly	fail	partly	fail	fail	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, partly. resource (https://api.blaxel.ai/v0/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Brave Search API, show the reasons Search and data	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://brave.com/auth.md/) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://brave.com/.well-known/oauth-protected-resource/) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://brave.com/.well-known/oauth-authorization-server/); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. HTTP 422 asking for a key, instead of a 401 challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Browser Use, show the reasons Browsers and scraping	1/7 +4 partly	partly	partly	fail	partly	fail	partly	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# Browser Use authentication for agents) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, partly. resource (https://api.browser-use.com/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. llms.txt mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	Browserbase, show the reasons Browsers and scraping	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. The metadata URL answers, but not with a JSON object 3. Sign-up by API, fail. Authorization server metadata is not usable; no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Cerebras, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.cerebras.ai/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.cerebras.ai/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.cerebras.ai/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 403 instead of 401: the body asks for a key, but there is no WWW-Authenticate challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Cloudflare, show the reasons Sandboxes and compute	1/7 +2 partly	partly	fail	fail	partly	fail	fail	pass
1. auth.md, partly. auth.md is published, and says agents cannot register here yet 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.cloudflare.com/.well-known/oauth-protected-resource/) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.cloudflare.com/.well-known/oauth-authorization-server/); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 403 instead of 401, with no WWW-Authenticate challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Cohere, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Coinbase Developer Platform, show the reasons Payments and billing	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. A Markdown page is served at /auth.md, but it is not about agent sign-in (it never mentions auth.md, agent_auth, or how an agent gets a credential) 2. Protected resource metadata, fail. The metadata URL answers, but not with a JSON object 3. Sign-up by API, fail. Authorization server metadata is not usable; no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. Corrected after review: the matched prose is about x402 products Coinbase offers (an Agentic Wallet tool that pays for x402 requests, x402 SDKs and a facilitator for sellers), not a way for an agent to pay Coinbase. The checker said partial: llms.txt mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Convex, show the reasons Databases and backend	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.convex.dev/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.convex.dev/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.convex.dev/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Daytona, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.daytona.io/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.daytona.io/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.daytona.io/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Deepgram, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	DigitalOcean, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.digitalocean.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.digitalocean.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.digitalocean.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	E2B, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	ElevenLabs, show the reasons LLM APIs	1/7 +2 partly	fail	partly	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, partly. resource (https://api.elevenlabs.io/v1/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	fal, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Fireworks AI, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Freestyle, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.freestyle.sh/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.freestyle.sh/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.freestyle.sh/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	GitHub, show the reasons Dev tools	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	GitLab, show the reasons Dev tools	1/7 +2 partly	fail	partly	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md answers with a Cloudflare bot challenge (after a redirect to https://gitlab.com/users/sign_in) 2. Protected resource metadata, partly. resource (https://gitlab.com/api/v4/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Google Cloud, show the reasons Sandboxes and compute	1/7	fail	fail	fail	pass	fail	fail	fail
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. The metadata URL answers, but not with a JSON object 3. Sign-up by API, fail. Authorization server metadata is not usable; no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, pass. 401 with a Bearer challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://cloud.google.com/llms.txt answers with an HTML page; https://cloud.google.com/docs/llms.txt not found (HTTP 404) (after a redirect to https://docs.cloud.google.com/docs/llms.txt)
33	Google Gemini API, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 403 instead of 401: the body asks for a key, but there is no WWW-Authenticate challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Groq, show the reasons LLM APIs	1/7 +2 partly	fail	fail	fail	partly	partly	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, partly. llms.txt mentions spend limits in prose; no machine-readable cap 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Heroku, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.heroku.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.heroku.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.heroku.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Hetzner Cloud, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.hetzner.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.hetzner.com/.well-known/oauth-protected-resource/) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.hetzner.com/.well-known/oauth-authorization-server/); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Hyperbrowser, show the reasons Browsers and scraping	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.hyperbrowser.ai/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.hyperbrowser.ai/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.hyperbrowser.ai/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Inkbox, show the reasons Email, phone and messaging	1/7 +3 partly	fail	partly	partly	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, partly. resource (https://inkbox.ai/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, partly. llms.txt links an agent sign-up guide (https://inkbox.ai/docs/get-started/agent-signup.md), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Linear, show the reasons Dev tools	1/6	fail	fail	fail	not run	fail	fail	pass
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, not run. GraphQL API that takes queries by POST only; this checker sends GET requests only 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Mistral, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Modal, show the reasons Sandboxes and compute	1/6 +1 partly	fail	fail	fail	not run	partly	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, not run. Modal has no public REST API to probe (its SDK and CLI talk gRPC) 5. Spend limits, partly. llms.txt mentions budgets in prose; no machine-readable cap 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Morph Cloud, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.morph.so/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.morph.so/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.morph.so/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	NanoGPT, show the reasons LLM APIs	1/7 +5 partly	partly	partly	fail	partly	partly	partly	pass
1. auth.md, partly. auth.md is published, but documents no registration endpoint the checker recognizes (it describes OAuth, device login or keys the person makes) 2. Protected resource metadata, partly. resource (https://nano-gpt.com/api/v1) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, partly. auth.md mentions usage_limit_type in prose; no machine-readable cap 6. Payment handoff, partly. llms.txt mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Netlify, show the reasons Sandboxes and compute	1/7 +2 partly	partly	fail	fail	partly	fail	fail	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# Authenticating AI agents with Netlify) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Northflank, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	OpenRouter, show the reasons LLM APIs	1/7 +2 partly	fail	fail	fail	partly	partly	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, partly. llms.txt mentions credit limits in prose; no machine-readable cap 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Orthogonal, show the reasons Search and data	1/7 +3 partly	fail	fail	partly	partly	fail	partly	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.orthogonal.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.orthogonal.com/.well-known/oauth-protected-resource) 3. Sign-up by API, partly. llms.txt links an agent sign-up guide (https://www.orthogonal.com/agent-signup.md), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. llms.txt mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	Paddle, show the reasons Payments and billing	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.paddle.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.paddle.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.paddle.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 403 instead of 401: the body asks for a key, but there is no WWW-Authenticate challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
33	Parallel, show the reasons Search and data	1/7 +4 partly	partly	fail	partly	partly	fail	partly	pass
1. auth.md, partly. An agent sign-in guide is published at /auth.md, but its heading (# Agent Authentication) does not name auth.md, so tools looking for the spec may skip it 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, partly. auth.md documents a sign-up API (https://platform.parallel.ai/agent/identity), but there is no agent_auth metadata for tools to find it 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. auth.md mentions a payment path (top up balance — `POST /service/v1/balance) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	Pinecone, show the reasons Databases and backend	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.pinecone.io/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.pinecone.io/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.pinecone.io/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Postmark, show the reasons Email, phone and messaging	1/7 +2 partly	partly	fail	fail	partly	fail	fail	pass
1. auth.md, partly. auth.md is published, but documents no registration endpoint the checker recognizes (it describes OAuth, device login or keys the person makes) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Render, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Replicate, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Replit, show the reasons Sandboxes and compute	1/6	fail	fail	fail	not run	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, not run. Replit has no public REST API for accounts to probe 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Runloop, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	RunPod, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.runpod.io/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	ScrapingBee, show the reasons Browsers and scraping	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.scrapingbee.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.scrapingbee.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.scrapingbee.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. HTTP 400 asking for a key, instead of a 401 challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	SerpApi, show the reasons Search and data	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Steel, show the reasons Browsers and scraping	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Stripe, show the reasons Payments and billing	1/6	fail	fail	fail	not run	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, not run. not probed: this run's tooling does not call Stripe's API 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. Corrected after review: the matched prose is about products Stripe sells (MPP and x402 for merchants, Stripe Climate donations), not a way for an agent to pay Stripe. The checker said partial: llms.txt mentions a payment path (HTTP 402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	Tavily, show the reasons Search and data	1/7 +2 partly	fail	fail	fail	partly	fail	partly	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.tavily.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.tavily.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.tavily.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, partly. llms.txt mentions a payment path (x402) in prose; nothing machine-readable 7. Docs in Markdown, pass. llms.txt found
33	Together AI, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.together.ai/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Turso, show the reasons Databases and backend	1/7 +2 partly	fail	partly	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, partly. resource (https://mcp.turso.ai/mcp) does not match the URL the metadata came from; RFC 9728 section 3.3 says a client MUST NOT use it 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Upstash, show the reasons Databases and backend	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Vapi, show the reasons Email, phone and messaging	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	Vercel, show the reasons Sandboxes and compute	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 403 instead of 401: the body asks for a key, but there is no WWW-Authenticate challenge 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found
33	xAI, show the reasons LLM APIs	1/7 +1 partly	fail	fail	fail	partly	fail	fail	pass
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. Corrected after review: the only match is the consumer X subscription page ("Spending caps and alerts"), not the API. The checker said partial: llms.txt mentions spending caps in prose; no machine-readable cap 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, pass. llms.txt found at a docs path
93	CodeSandbox, 6 not read, show the reasons Sandboxes and compute	0/7 +1 partly 6 not read	not read	not read	not read	partly	not read	not read	not read
1. auth.md, not read. Not read on 2026-11-12: https://codesandbox.io/auth.md answered with a Cloudflare bot challenge 2. Protected resource metadata, not read. Not read on 2026-11-12: https://codesandbox.io/.well-known/oauth-protected-resource answered with a Cloudflare bot challenge 3. Sign-up by API, not read. Not read on 2026-11-12: https://codesandbox.io/.well-known/oauth-authorization-server answered with a Cloudflare bot challenge 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, not read. Not read on 2026-11-12: https://codesandbox.io/.well-known/oauth-authorization-server answered with a Cloudflare bot challenge 6. Payment handoff, not read. Not read on 2026-11-12: https://codesandbox.io/.well-known/x402 answered with a Cloudflare bot challenge 7. Docs in Markdown, not read. Not read on 2026-11-12: https://codesandbox.io/llms.txt answered with a Cloudflare bot challenge
93	DeepSeek, show the reasons LLM APIs	0/7 +1 partly	fail	fail	fail	partly	fail	fail	fail
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://deepseek.com/llms.txt not found (HTTP 404); https://api-docs.deepseek.com/llms.txt answers with an HTML page
93	Deno Deploy, 1 not read, show the reasons Sandboxes and compute	0/7 +1 partly 1 not read	fail	fail	fail	partly	fail	fail	not read
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. The metadata URL answers, but not with a JSON object 3. Sign-up by API, fail. Authorization server metadata is not usable; no sign-up API is documented in auth.md or llms.txt (not read on 2026-11-12: https://docs.deno.com/llms.txt answered with HTTP 500) 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt (not read on 2026-11-12: https://docs.deno.com/llms.txt answered with HTTP 500) 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt (not read on 2026-11-12: https://docs.deno.com/llms.txt answered with HTTP 500) 7. Docs in Markdown, not read. Not read on 2026-11-12: https://docs.deno.com/llms.txt answered with HTTP 500
93	Jina AI, show the reasons Search and data	0/7 +2 partly	fail	fail	fail	partly	fail	fail	partly
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, partly. A text file is served at llms.txt, but it does not start with an H1 (the one section llmstxt.org requires)
93	Koyeb, show the reasons Sandboxes and compute	0/7 +1 partly	fail	fail	fail	partly	fail	fail	fail
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.koyeb.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.koyeb.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.koyeb.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://koyeb.com/llms.txt not found (HTTP 404) (after a redirect to https://www.koyeb.com/llms.txt); https://www.koyeb.com/docs/llms.txt not found (HTTP 404)
93	Lemon Squeezy, show the reasons Payments and billing	0/7 +1 partly	fail	fail	fail	partly	fail	fail	fail
1. auth.md, fail. /auth.md not found (HTTP 404) (after a redirect to https://www.lemonsqueezy.com/auth.md) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) (after a redirect to https://www.lemonsqueezy.com/.well-known/oauth-protected-resource) 3. Sign-up by API, fail. Authorization server metadata not found (HTTP 404) (after a redirect to https://www.lemonsqueezy.com/.well-known/oauth-authorization-server); no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://lemonsqueezy.com/llms.txt not found (HTTP 404) (after a redirect to https://www.lemonsqueezy.com/llms.txt); https://lemonsqueezy.com/docs/llms.txt not found (HTTP 404) (after a redirect to https://docs.lemonsqueezy.com/llms.txt)
93	SendGrid, show the reasons Email, phone and messaging	0/7 +1 partly	fail	fail	fail	partly	fail	fail	fail
1. auth.md, fail. /auth.md answers with an HTML page, not Markdown 2. Protected resource metadata, fail. Protected resource metadata answers HTTP 403 3. Sign-up by API, fail. Authorization server metadata answers HTTP 403; no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://sendgrid.com/llms.txt answers with an HTML page; https://sendgrid.com/docs/llms.txt not found (HTTP 404) (after a redirect to https://www.twilio.com/docs/sendgrid/llms.txt)
93	Sprites, show the reasons Sandboxes and compute	0/7 +1 partly	fail	fail	fail	partly	fail	fail	fail
1. auth.md, fail. /auth.md not found (HTTP 404) 2. Protected resource metadata, fail. Protected resource metadata not found (HTTP 404) 3. Sign-up by API, fail. Authorization server metadata has no agent_auth block, and no sign-up API is documented in auth.md or llms.txt 4. Key works without a browser, partly. 401, but no WWW-Authenticate header (RFC 9110 section 15.5.2 says the server MUST send one) 5. Spend limits, fail. No spend cap in metadata, auth.md or llms.txt 6. Payment handoff, fail. No 402, payment challenge or billing metadata, and no payment path the checker recognizes in auth.md or llms.txt 7. Docs in Markdown, fail. https://sprites.dev/llms.txt not found (HTTP 404); https://sprites.dev/docs/llms.txt not found (HTTP 404)

The seven checks.

Each is checked against a public spec or draft. Each passes, passes partly, or fails.

1
auth.md
Does /auth.md tell an agent how to register, in the shape of the auth.md spec?
Checked against WorkOS auth.md, AUTH.md v0.6.0
13 of 100 pass
13 pass · 15 partly · 70 fail · 2 not read
2
Protected resource metadata
Is there RFC 9728 metadata that names the authorization server?
Checked against RFC 9728, sections 2, 3 and 3.3
18 of 100 pass
18 pass · 15 partly · 66 fail · 1 not read
3
Sign-up by API
Can an agent find an API endpoint that creates an account, with no web form or CAPTCHA?
Checked against auth.md Step 1b (agent_auth in RFC 8414 metadata)
10 of 100 pass
10 pass · 10 partly · 79 fail · 1 not read
4
Key works without a browser
Does a signed-out API call get a 401 with a WWW-Authenticate challenge, not a login page or a bot wall?
Checked against RFC 9110 section 15.5.2; RFC 6750 section 3; RFC 9728 section 5.1
20 of 95 pass
20 pass · 75 partly · 0 fail · not run on 5
5
Spend limits
Can an agent read the spend cap its key will have?
Checked against auth-md-spend-limits 0.1 (draft, Prized); draft-hardt-aauth-budgets-00
0 of 100 pass
0 pass · 6 partly · 93 fail · 1 not read
6
Payment handoff
When money is needed, is there a machine-readable way for the agent to say so and hand over?
Checked against RFC 9110 section 15.5.3 (402); x402 v2 HTTP transport; draft-httpauth-payment; auth-md-spend-limits section 4
2 of 100 pass
2 pass · 9 partly · 88 fail · 1 not read
7
Docs in Markdown
Is there an llms.txt an agent can read?
Checked against llms.txt (llmstxt.org)
91 of 100 pass
91 pass · 1 partly · 6 fail · 2 not read

Each check passes, passes partly, or fails. Partly means the platform publishes something the check looks for, but short of the spec: it says it only in prose an agent can read, its file departs from the spec’s shape (a heading, a field, or a resource clients must not use), or the file stops short, such as an auth.md that says agents cannot register yet or metadata that names no authorization server. For the key check, partly is an API that refuses the signed-out call, usually with a 401, but without the WWW-Authenticate header the spec requires. That check sends no key. A check is not read when it would be a fail and one of its own files gave no answer: a server error, a 429, a bot wall, a failed connection, or a request the script’s own cap stopped (the dated run asks twice before it says so). That is not a fail: the reason says what happened at the URL and on which date, and the check still counts in the platform’s total. Sign-up by API, spend limits and payment handoff also read auth.md and llms.txt for prose; when only those went unread, the check stays a fail and its reason names the file.

Show your result.

A platform in the table can show its result from November 12, 2026 with this badge. It says the date, and it links back to the platform’s row. It changes only when a new run is published.

Fixed something since? Check your domain for your live score beside your row, what changed, and a link to re-run it after each fix.

Platform

Markdown

[![Agent sign-up check result for prized.dev](https://prized.dev/agent-signup-check/badge/prized.dev.svg)](https://prized.dev/agent-signup-check?utm_source=badge&utm_campaign=prized.dev#prized.dev)

HTML

<a href="https://prized.dev/agent-signup-check?utm_source=badge&amp;utm_campaign=prized.dev#prized.dev"><img src="https://prized.dev/agent-signup-check/badge/prized.dev.svg" alt="Agent sign-up check result for prized.dev"></a>

How it checks.

Read-only, from public files, with one script for every platform.

Think a result is wrong? or open an issue.

GET requests only, to files published for agents, to one documented API URL without a key, and sometimes to one made-up path that tells a real auth.md from a page a site serves at every path. Nothing is posted, no account is made, and no credential is sent. At most 24 requests per check of a platform, redirects included; a run checks a platform a second time when a request got no answer (a network failure, a server error, a 429 or a bot wall).
https on port 443 only, public addresses only, 1 MB and 8 seconds per response. The script names itself in its User-Agent (PrizedAgentSignupCheck/0.2.5, with a link to this page).
For 95 of the 100 platforms we picked one documented API endpoint that needs a key; the results file lists it. GraphQL-only APIs and platforms with no public REST API were not probed, and neither was Stripe, whose API the tooling that makes the run does not call. Those rows count six checks, so six is the most they can pass.
Protected resource metadata is looked for at the URL the probed API’s 401 names, then on the site’s own host, then on the API’s host (also for a GraphQL API that is not probed). Authorization server metadata is read from the first server named in protected resource metadata that a client may use, or else from the site’s own host, then the API’s host. For protected resource metadata, a separate MCP server host is read only when the site’s or the API host’s well-known path redirects there, or the API’s 401 points there; the check does not go to a host for it because auth.md or llms.txt names that host. Netlify, Cloudinary and Render, among others, publish protected resource metadata for their MCP servers on separate hosts, so they fail that check.
A check sees what a platform publishes, not what happens after a sign-up form is sent. A platform that lets agents in through a CLI or SDK it never describes in a public file scores lower here than it would in use. A check that would fail while one of its own files gave no answer (a bot wall, a server error, a 429, a failed connection, or a request the script’s own cap stopped) is shown as not read, with what happened at the file’s URL and the date; it is not counted as a fail, and it is not a pass. A bot wall in front of the API itself still fails the key check.
Three verdicts were corrected by hand after review, where the script matched text about something else: Coinbase Developer Platform (payment handoff), Stripe (payment handoff) and xAI (spend limits). Each reason in the results says so and gives the script’s own verdict.
Prized wrote this checker, picked the platforms, and wrote the spend-limits draft that two of the checks accept. Prized is one of the platforms listed under sandboxes and compute and competes with others in that group. The payment check’s prose patterns for billing_url and billing_required were added after reading Prized’s and Boat’s auth.md; they apply to every platform. Prized is scored by the same code as everyone else and sorted with them.
This is one dated run. Platforms change their files; run the script again for today’s answer.

Run it on your own domain.

One Node file, Node 18 or later, no dependencies. It runs the same seven checks this page does.

curl -fsSLO https://prized.dev/agent-signup-check.mjs
node agent-signup-check.mjs example.com --api https://api.example.com/v1/me

Check a domain Source on GitHub

Can an agent sign up here?

100 platforms,November 12, 2026.

The seven checks.

auth.md

Protected resource metadata

Sign-up by API

Key works without a browser

Spend limits

Payment handoff

Docs in Markdown

Show your result.

How it checks.

Run it on your own domain.

100 platforms,
November 12, 2026.