Inkling 2 Small vs Router.com (Ramp Router)

Inkling 2 Small 20

Published rubric. No payment protocol (0). Per-million-token prices for serverless inference and training published without a login on 6 November (20). No free tier listed, and the quickstart asks for payment details before training, per the tinker listing (0). Sign-up is a browser flow (0). 0 + 20 + 0 + 0 = 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).

Inkling 2 Small 75

Model reading. Released 5 November 2026 (30). Churn and notice in place of release counts: Inkling, Inkling-Small (30 July) and Inkling 2 Small in about four months, and a deprecations page with dated retirements and a promise to 'aim to give advance notice' by email, with no stated period, per the tinker listing (10 of 20). A public changelog and a support address and Discord, per the tinker listing (10 of 15). Current official SDKs, Tinker's Python SDK and the OpenAI-compatible endpoint (15). SDK and cookbook CI, per the tinker listing (10). 30 + 10 + 10 + 15 + 10 = 75.

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

Inkling 2 Small 62

Model reading (tool use, structured output, caching, context, batch, SDKs). A 256K served context, max_tokens and a priced cache at $0.03 per million; tool use isn't documented for this model (15 of 25). Output-size controls through max_tokens, reasoning_effort and separate_reasoning (15 of 20). One documented error, the 400 for unsupported reasoning_effort (5 of 20). Stable request IDs make SDK sampling retries safe, per the tinker listing (15 of 20). OpenAI's SDKs work against the endpoint, with Tinker's Python SDK besides, and reasoning defaults to 0.9 (12 of 15). 15 + 15 + 5 + 15 + 12 = 62.

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

Inkling 2 Small 70

Model reading. No OpenAPI file of its own; the OpenAI-compatible chat and completions endpoints and the typed Python SDK are the contract, as the tinker listing reads it (15). llms.txt on the docs host, per the tinker listing's 1 October check (10). The model card states intended use (agentic and tool-use systems, coding assistants, chatbots, RAG), inputs, outputs and limitations, and the launch post its benchmarks (16 of 20). Model IDs, context lengths and the reasoning_effort values (none to xhigh, or 0.0 to 0.99) are documented; the tool-call format and structured output aren't, for this model (8 of 15). A Python example and an HTTP 400 for models without reasoning_effort, with no error page (6 of 15). A dated Tinker changelog and a model deprecations page, per the tinker listing (15). 15 + 10 + 16 + 8 + 6 + 15 = 70.

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

Inkling 2 Small 57

Platform readings are the tinker listing's. Revocable API keys from the console, with no per-key scopes found (20). Org, team and project permissions with no read-only role (5). The model returns its own completions, no third-party content (10). get_audit_log() for admins (15). security.txt with a reporting address and no stated acknowledgement time (7). For the model reading, Tinker's terms commit not to use Customer Content for training, recorded under transparency. 20 + 5 + 10 + 15 + 7 = 57.

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

Inkling 2 Small 30

Model reading, for the surface it's called on, Tinker's serverless inference and OpenAI-compatible API. No status page found, per the tinker listing's checks of 1 October and 4 November (0), so no readable incident history (5). The only published limit is the in-flight sample cap of 2,000, per the tinker listing's 1 October check; the OpenAI-compatible page gives no numbers and says higher or more stable throughput needs the waitlist (10). The SDK retries sampling with stable request IDs, per the tinker listing's reading of the SDK repository; the OpenAI-compatible page has no retry guidance (15). No SLA found (0). Serverless inference is 'currently in beta' on the models and pricing page and the OpenAI-compatible API is labelled Beta, read 6 November (0). 0 + 5 + 10 + 15 + 0 + 0 = 30.

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.