Skip to content
Good for Bots

Zerouter

zerouter.ai

API gateway providing a single key and base URL for Claude, GPT, Gemini, Grok, and Kimi

Good for Bots: Fair, 68 of 100Get this badge →

On your homepage, it turns this report’s link to zerouter.ai dofollow.

Scanned

What is Zerouter?

Zerouter is an AI API gateway and OpenRouter alternative designed for developers. It provides a single API key to access multiple frontier language models including Claude, GPT, Gemini, Grok, and Kimi. The service allows users to change only the base URL and key in tools such as Claude Code, Codex CLI, and Cursor without modifying prompts or clients. Zerouter operates on a prepaid pay-as-you-go model billed per million tokens without requiring a monthly subscription.

Through a bot’s eyes

“Zerouter is an AI API gateway providing a single API key and drop-in base URL to access frontier models from Claude, GPT, Gemini, Grok, and Kimi on a pay-per-token basis.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns about an API gateway service that routes requests to major AI model families. The text covers specific model identifiers, endpoint configurations, and pricing structures per one million tokens for providers such as Anthropic, OpenAI, Google, xAI, and Alibaba Cloud. The input provides concrete technical integration details for tools like Claude Code, Codex CLI, and Cursor, alongside instructions for configuration settings and base URLs. The provided llms.txt file adds a comprehensive list of model identifiers, exact token pricing comparisons against official list prices, and direct documentation links. The JSON-LD schema confirms organization details and structured software application attributes, while the homepage input demonstrates dashboard elements, session handling, and sample requests.

Good for Bots report

Zerouter scores 68 of 100: 44 of the 50 base points, 24 of the 50 agent-layer points, no penalties.

Earned

44 of the 50 base points above the line, 24 of the 50 agent-layer points below it.

68

Still open

Behind the checks below, with prompts in Pro.

4
Penalties0
How scoring works · current methodology →

For the owner of zerouter.ai

3 prompts, 28 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

43.8 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 2 user-agent groups.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 102 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, ImageObject, WebSite in valid schema.org JSON-LD.

Half passes.

5 of 10 points.

1 of 4 pages read pass; 3 partly. The homepage is partly structured: 2 visible content roots, where the standard allows one.

Passes.

8.3 of 8.3 points.

70 of 70 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

274 of 274 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.

Half passes.

1.3 of 2.5 points.

277 of 278 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Prompt in Pro →
Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

24.4 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 53 links across 5 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Passes.

5 of 5 points.

States a position on 12 AI crawlers, across 3 purposes (training, search, user-fetch).

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1475 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 1 redirect.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 741 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /auth.md, so the authentication document could not be verified.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://www.zerouter.ai/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://zerouter.ai/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • webzio-extended (ai-training)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://www.zerouter.ai/

    https://www.zerouter.ai/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

  • Declared allow · robots.txt

    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • duckassistbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • applebot-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • google-extended (ai-training, grounding)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://www.zerouter.ai/

    https://www.zerouter.ai/robots.txt

    User-agent: gptbot
    User-agent: oai-searchbot
    User-agent: chatgpt-user
    User-agent: claudebot
    User-agent: claude-searchbot
    User-agent: claude-user
    User-agent: perplexitybot
    User-agent: perplexity-user
    User-agent: google-extended
    User-agent: applebot-extended
    User-agent: bingbot
    User-agent: duckassistbot
    User-agent: mistralai-user
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

24th of 57 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 24Zerouter · this reportzerouter.ai

The prompts in the owner view would take Zerouter to 96, 2nd in its category.

To the prompts →

Category average 63. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
2 Nov 2026
Rubric
0.9.0
Requests
24
Fetched
2.2 MB
Took
27.5 s
Homepage
741 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /docs/claude-codedocumentation · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /docscollection · linked from the homepage · from the sitemap · read

Do you run zerouter.ai? Open the owner view → Removing the listing is free. Remove →