Claude Fable 5.2 vs Router.com (Ramp Router)

Claude Fable 5.2 60

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Status page at status.claude.com with component history (20). The last 90 days carry several major and two critical API incidents, among them Fable 5.1 and Mythos 5.1 on 3 September and Fable 5.1 on 23 and 25 October, so 0 for incident history. Rate limits published per model, Fable 5.x at 4,000 requests a minute at the Start tier (15). 429s with retry-after and SDK retries with backoff (15). No SLA on sale (0). The model page lists it as a current model with no preview label (10). 20 + 0 + 15 + 15 + 0 + 10 = 60. Graded by an agent running on Claude, by the same checklist as every other listing.

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.

Claude Fable 5.2 90

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. The SDK-bundled OpenAPI file as half a contract (15 of 25, the Claude API listing's judgement call). llms.txt with Markdown twins (10). The model page, what's new and the migration guide say what changed from Fable 5.1 and what to send and not send (forced tool choice, sampling parameters, computer_20251124 returning 400 except on Bedrock), read 9 November (20). Structured outputs and strict tools GA (15). Documented error types with request_id (15). anthropic-version and dated release notes (15). 15 + 10 + 20 + 15 + 15 + 15 = 90.

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).

Claude Fable 5.2 91

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Released 9 November 2026 beside dated release notes several times a week (30). 60 days' minimum notice for retirements, and the model page says retirement not sooner than 9 November 2027 (8 of 12, the Claude API's reading). Model shutdowns kept to notice (8). Support centre and dated notes (15). The sampled SDK issue without a reply, per the 1 October check (5 of 10). Current SDKs (15). Runtimes stated (10). 30 + 8 + 8 + 15 + 5 + 15 + 10 = 91.

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).

Claude Fable 5.2 92

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Workspace-scoped keys with expiry and Workload Identity Federation, no scopes below the workspace (25 of 30). No training on API data without express permission (20). The model requires 30-day retention, is a Covered Model and is outside ZDR unless Anthropic expressly authorises it, per the model page read 9 November, the same as Fable 5.1 (12 of 15). Usage and cost analytics, Compliance API and OpenTelemetry export (15). security.txt, HackerOne and SOC 2, ISO 27001 and ISO 42001 (20). Thinking blocks work only in the account that produced them or one linked to it, per the model page. 25 + 20 + 12 + 15 + 20 = 92.

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).

Claude Fable 5.2 85

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Commercial Terms with named contracting parties and Apache 2.0 SDKs (15). Retention stated two ways across the docs and the privacy centre, though for this model the model page is plain that 30 days is required (20 of 30, kept at the platform's reading). Deprecation page with dates, and this model's retirement floor on its page (20). Processing countries and subprocessors named (20). The benchmark figures are Anthropic's own, with no third-party run of this model found on 9 November. 15 + 20 + 20 + 20 = 75.

Router.com (Ramp Router) 64

Closed service. The Router Terms of Service, Router Privacy Notice and Provider Schedule render only with JavaScript. Their 27 October readings came from the legal site's script and are no longer counted, so the lines resting on them are held, as on ramp. The CLI is MIT (16 of 30). The docs FAQ states the one-year default recording, the opt-out and the PII step, and links Ramp's general privacy policy. Every link to the Router Privacy Notice answers 301 to that general policy (16 of 30). No deprecation policy found, and model retirements in the docs carry no dates (5 of 20). The docs FAQ names the providers whose infrastructure runs the models, says all models run on US infrastructure and points to the Provider Schedule for provider retention terms. No Router subprocessor list was found (13 of 20).

Claude Fable 5.2 95

Model reading for claude-fable-5-2 on the Claude API. Platform facts are the Claude API listing's (anthropic-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Tool use with parallel calls, 15 of 20 because tool_choice any or tool returns a 400 invalid_request_error, per the model page read 9 November. Structured outputs (15). Prompt caching with reads at $0.20, 0.025x input, per the pricing page read 9 November (15). 1M context by default and at most, 128K output (15). Batch at half price (10). Official SDKs in seven languages (10). Documented errors, retry-after and retries (15). 15 + 15 + 15 + 15 + 10 + 10 + 15 = 95.

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).