Head to head · LLM inference · October 2026 research run

Router.com (Ramp Router) vs xAI API (Grok)

xAI API (Grok) scores 71.7 (BB) on agent readiness against Router.com (Ramp Router)'s 53.7 (D), and leads in 5 of 7 scored categories. Router.com (Ramp Router) leads on payments & pricing. Both do llm inference.

Best model APIs and inference for AI agents · All 830 models comparisons

Which one, for what

Router.com (Ramp Router) D

Best for Teams in the US that want one key for OpenAI, Anthropic, xAI and open-weight models, with routing to cheaper tiers and per-request cost, and can switch off content recording.

Ahead on

  • Payments & pricing, 40 against 20

Watch for

Ramp-side content recording is on by default and keeps prompts, outputs and tool calls for one year

xAI API (Grok) BB

Best for Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing.

Ahead on

  • Reliability, 55 against 22
  • Schema & documentation, 88 against 58
  • Agent ergonomics, 90 against 77
  • Security & auth, 97 against 66
  • Maintenance & community, 77 against 59

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

API models outage of about 3 hours 40 minutes on 3 September 2026, and high error rates on grok-4.6 and grok-4.5 on 17 August

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability xAI API (Grok) +33

Router.com (Ramp Router) 22

Hosted reading. No status page found. status.router.com still does not resolve on 4 November, router.com/status answers 404, and neither the docs nor router.com link one (0). No readable incident history (5). No request or token rate limits are published. The docs say limits vary by model and list only technical limits, a 100 MiB body, 15 candidates and 100 keys per user (0). The errors page passes through provider retry-after and retry-after-ms, tells clients to respect them, gives a retry or fallback action for every 4xx and 5xx code, says retrying a 501 unchanged won't help and that a failed fallback candidate is not retried, and the fallbacks guide says truncated attempts are billed on top of later attempts. No idempotency key exists for the generation call that starts billing, so this is safe-retry guidance without keys (12). No SLA found in the docs or on router.com (0). The public API carries no beta label in the docs, and the docs llms.txt, re-read on 4 November, still says to treat 'beta pricing, limits, and enterprise controls as subject to change'. A 27 October reading of Ramp's product schedule came from the legal site's script and is no longer counted, so the line keeps its earlier partial value (5 of 10). 0 + 5 + 0 + 12 + 0 + 5 = 22.

xAI API (Grok) 55

Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10).

Security & auth xAI API (Grok) +31

Router.com (Ramp Router) 66

Router, read on the model lines. Router keys are shown once, can expire, carry lifetime or periodic spend caps, can be locked, unlocked or revoked, and each key has its own model set and default workload. No permission scopes or programmatic rotation were found (24 of 30). The docs FAQ says Ramp-side content recording is on by default and keeps inputs, outputs and tool calls for one year for debugging, semantic analysis and product improvement, with detected personal data removed before product use. Provider training terms are in Ramp's Provider Schedule, which renders only with JavaScript. Its 27 October reading came from the legal site's script and is no longer counted, so the line is held (6 of 20). Recording can be switched off account-wide, propagating asynchronously and without deleting existing archives, and flagged content may still be kept up to 30 days. The docs FAQ points to the Provider Schedule for zero data retention policies and exceptions, which could not be read, so the line is held (10 of 15). Logs show model, provider, status, tokens, cost, latency, fallback candidates, credential source and routing decisions per request, with usage export to S3 for Router Admins (14 of 15). A valid security.txt on router.com points to Ramp's security address. Ramp's SOC 2 and ISO 27001 reports, per the ramp listing's 8 October check, were not shown to cover Router, which is a separate product under its own terms. No bug bounty found (12 of 20).

xAI API (Grok) 97

Model reading. Team API keys with ACLs per endpoint and per model, QPM and TPM caps, expiry, and create, rotate, disable and delete through the Management API, plus documented mTLS. GitHub secret scanning disables leaked keys and emails the owner (30). The security FAQ says SpaceXSI never trains on API inputs or outputs without explicit permission (20). Requests and responses are kept 30 days for abuse auditing, then deleted, and team admins can switch on zero data retention themselves, confirmed by an x-zero-data-retention header on every response (15). Console audit log and a Management API audit-events endpoint, plus optional per-key request logging (15). security.txt valid to 2027-06-29 with a HackerOne bug bounty and a separate safety contact for prompt-injection issues. SOC 2 Type 2 is claimed in the security FAQ with the reports behind an NDA in the trust centre, so 17 of 20. Remote MCP doesn't support require_approval, which the model checklist doesn't score but reviewers should see. New in October, a guidelines array lets the caller make the model decline nsfw, violence or profanity content, which the checklist doesn't score.

Schema & documentation xAI API (Grok) +30

Router.com (Ramp Router) 58

Router, scored on the API lines. No OpenAPI or other machine-readable contract found. /openapi.json on docs.router.com returns the docs app shell. The API follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a router, the same reading as RouterPlus (0 of 25). llms.txt and a Markdown copy of every page at the same path with .md (10). Pages say which endpoint to prefer and why, what isn't served (embeddings, files, batches), which Chat Completions controls return 501, and which workload suits which job (17 of 20). Router-only fields are tabled with types and bounds, the route selector rules are stated (model or models but never both, 1 to 15 candidates), over-limit timeouts are a 400 naming the maximum, and the model list documents a typed router object with a schema_version. Request bodies otherwise follow the upstream formats (12 of 15). curl, OpenAI SDK, Anthropic SDK, LangChain, Vercel AI SDK, LlamaIndex and Pydantic AI examples, and an error reference with a status, code and action for each case (15). Paths sit under /v1 and the model object is versioned, but no API changelog or dated release notes were found (4 of 15).

xAI API (Grok) 88

OpenAPI 3.1 document at docs.x.ai/openapi.json, 39 paths and 205 schemas on 6 November, covering Responses, Chat Completions, files, images, videos and models. The batch endpoints documented in the REST reference still aren't in it (20 of 25, applied as for gemini-api's missing Interactions API). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). The models page says which model to use for code, chat, images, video and voice, and reference pages list each parameter. Reference not read in full (18 of 20). Structured outputs are guaranteed to match the schema for supported keywords, and tool arguments always conform with strict implicitly true (15). Examples in Python, JavaScript and curl on every guide. The debugging page lists status codes with fixes, but the cause cells for 400, 403, 404 and 415 are still empty (13 of 15). Release notes are grouped by month without day dates, and model slugs come as aliases and dated versions (12 of 15).

Payments & pricing Router.com (Ramp Router) +20

Router.com (Ramp Router) 40

No x402, MPP or L402 in any of the 41 docs pages. Calls draw on account credit (0). Per-token prices for every model are public at router.com/models and in the supported-models page without a login (20). Router.com says routing is free through 2026 and the first $26 of credits are free, and BYOK requests carry no Router charge. We did not sign up to confirm that no card is asked for (20). A person signs up in the browser with a US business email or Sign in with Ramp, and the CLI creates keys only after browser approval (0).

xAI API (Grok) 20

No x402, MPP or L402 (0). Per-token and per-call prices published without a login on docs.x.ai/developers/pricing (20). No free tier found for the text API, and the quickstart says to load the account with credits (0). Sign-up is in the browser at console.x.ai. The Management API can create keys and top up prepaid credit, but only with a management key made by a person in the console, so no line credit (0).

Maintenance & community xAI API (Grok) +18

Router.com (Ramp Router) 59

Router, read on the model lines for a closed service. The Ramp CLI that ships the router commands tagged v0.2.91 on 3 November 2026, a release that changes router.py and router_credentials.py, one of 81 tags since 6 August (30). Models carry a deprecated status and the docs list deprecated and retired models, but no notice period is stated, and the Baseten retirement note gives no date and says requests aren't redirected (4 of 12). Provider-specific Baseten ids and several Fireworks models were retired without dates. The API host moved from router-api.ramp.com to api.router.com, and the old host still answers (3 of 8). No public API changelog. Support is a dashboard button and router@ramp.com, not tested (5 of 15). ramp-cli issue replies were not read, because GitHub's API wasn't available to this session (3 of 10). No API SDK. The Ramp CLI (MIT, npm @ramp/router and @ramp/cli, tagged v0.2.91 in the repository, Homebrew; npm itself not read) sets up agents and keys (7 of 15). The CLI repository has CI, build, npm and router-integration workflows and a tests folder, with 46 commit days since 29 July. ci.yml runs cargo test and pytest on pushes to main, and the results were not readable (7 of 10).

xAI API (Grok) 77

Model reading. grok-imagine-image-quality and grok-imagine-image-pro retired on 2 November 2026 as announced in September, Grok Voice 3.0 and custom moderation controls in October, Grok 4.7 on 21 September (30). No minimum notice period found. Retirements come as dated migration guides, retired slugs redirect to a replacement rather than failing, billed at the replacement's price, and grok-voice-2.0 was deprecated in October with no end date (4 of 12). Shutdowns in the last 90 days with dates given in advance, grok-voice-transcribe-1.0 on 2 October and grok-imagine-image-quality on 2 November (8 of 8). Release notes several times a month but dated only by month, support by email and a Discord #help channel, not tested. On xai-sdk-python a collaborator commented on 2 of the 16 most recent threads with replies, and most outside pull requests since 23 October are open without a maintainer reply (10 of 15, down from 12). The repository has CI, release and version-bump workflows (5 of 10). One current first-party SDK, xai-sdk 1.21.0 tagged on 23 October, Python only (10 of 15). Supported runtimes stated, Python 3.10 or later (10).

Agent ergonomics xAI API (Grok) +13

Router.com (Ramp Router) 77

Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on Responses, Messages and Chat Completions, and GET /v1/models reports tools.supported and parallel per model, with null where Router doesn't know. Behaviour depends on the model (16 of 20). The docs say JSON Schema output is expected to work across providers subject to model support, and each model carries a structured_outputs flag. A request the provider can't represent is a 501 (12 of 15). Cache read and write prices per model, a prompt_cache_key session lease of 5 or 30 minutes that keeps a session on the provider with a warm cache, and cache_control on Messages (14 of 15). Contexts up to 1,050,000 tokens on GPT-6.1 Sol and 1,048,576 on Kimi K3, a judgement call since a router has no default model (15). No batch route; the docs say Router doesn't serve batches (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, framework setups are documented, and the MIT Ramp CLI configures six coding agents (5 of 10). Typed codes for every error, a limit object naming the cap and who set it, an all-candidates-failed summary, request and trace ids on every response and the serving provider in a header (15).

xAI API (Grok) 90

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with parallel calls on by default and tool_choice of auto, required, none or a named function (20). Guaranteed structured outputs (15). Automatic prompt caching, cached input at 0.25x on grok-4.7 ($0.50 per million) and 0.16x on grok-4.3 (15). 500,000-token context on grok-4.7 and 1,000,000 on grok-4.3, 13 of 15 for the default model's 500K. The Batch API is now 20% off on grok-4.7, 4.6 and 4.5 as well as the older models, with batch requests outside the rate limits (10 of 10, up from 5 on 6 October). One first-party SDK, xai-sdk for Python, with the OpenAI SDKs and Vercel's AI SDK documented as alternatives (5 of 10). Status codes documented with fixes, no Retry-After header found (12 of 15).

Score by category

CategoryWeight this runRouter.com (Ramp Router)xAI API (Grok)Edge
Reliability16%202255xAI API (Grok) +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25888xAI API (Grok) +30
Agent ergonomics13%16.27790xAI API (Grok) +13
Security & auth14%17.56697xAI API (Grok) +31
Payments & pricing10%12.54020Router.com (Ramp Router) +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85977xAI API (Grok) +18
Transparency & trust7%8.86463Router.com (Ramp Router) +1
Negative events≤1500
TotalD 53.7/100BB 71.7/100

Facts side by side

FactRouter.com (Ramp Router)xAI API (Grok)
KindModel routerModel API
VendorRampSpaceXSI (xAI)
Hosted endpointhttps://api.router.com/v1https://api.x.ai/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceClosed service under the Router Terms of Service (last updated 31 August 2026). The Ramp CLI that configures coding agents for Router is MIT.Proprietary service under xAI's enterprise terms of service. The Python SDK is Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-032026-11-02
Terms last updatedcouldn't be read2026-10-27
Privacy policy last updatedcouldn't be read2026-10-27
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity1.7k npm/wk597 stars, 912k PyPI/wk

How the scores have moved

Verdicts

Router.com (Ramp Router)

Detailed Markdown docs with typed error codes, per-model capability data and routing an agent can set per request. No OpenAPI document, status page, changelog or published rate limits were found. Signup needs a US business email in a browser, and Ramp records prompts and outputs for a year by default unless switched off.

xAI API (Grok)

Grok 4.7 at $2/$6 per million tokens, now 20% off in batch, with a public OpenAPI spec, llms.txt, API keys limited by endpoint and model, and self-serve zero data retention. The API endpoints had a 3 hour 40 minute models outage on 3 September 2026, no SLA was found, and there's no free tier or first-party SDK beyond Python.

Before you call either

Router.com (Ramp Router)

  1. Switch off content recording in Settings before sending private data. It is on by default and keeps prompts and outputs for a year
  2. Read model ids from GET /v1/models at runtime. Ids are account-specific, an unknown one is a 404, and Gemini ids need your own Google key
  3. Use POST /v1/responses with a models list for fallbacks. Router stops falling back once a stream has started
  4. Set fallback_timeout and provider_timeout, or allow_flex_tier: false, when latency matters. Flex routing is on by default
  5. Treat both 401 invalid_api_key and 401 api_key_deactivated as a possibly locked key, and stop retrying on 402

xAI API (Grok)

  1. Build on the Responses API at https://api.x.ai/v1. Chat Completions is labelled deprecated and the Anthropic-compatible endpoint fully deprecated
  2. Pin a dated model slug. A retired slug keeps answering from a replacement model, billed at the replacement's price
  3. Back off exponentially on 429. The per-second cap is the per-minute budget divided by 48, with a minimum of 2
  4. Set allowed_tools on remote MCP servers. There's no approval step, and every exposed tool enters the context
  5. Use https://us.api.x.ai/v1 when processing must stay in the US. It costs 1.1x and serves only grok-4.7 and grok-4.6

Questions

Which is better for AI agents, Router.com (Ramp Router) or xAI API (Grok)?

xAI API (Grok) scores 71.7 (BB) on agent readiness against Router.com (Ramp Router)'s 53.7 (D), and leads in 5 of 7 scored categories. Router.com (Ramp Router) leads on payments & pricing.

Do Router.com (Ramp Router) and xAI API (Grok) need an API key?

Both need an API key.

Can an agent call Router.com (Ramp Router) and xAI API (Grok) without installing anything?

Yes. Router.com (Ramp Router) has a hosted endpoint at https://api.router.com/v1 and xAI API (Grok) at https://api.x.ai/v1.

Other comparisons with Router.com (Ramp Router) or xAI API (Grok)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.