Ramp Router
$26 for new accounts; it does not recur.
https://api.router.com/v1Models mentioned
The offer covers a dynamic catalog, provider-selected route, or model class without stable model IDs in this snapshot.
Equivalent paid value
How this was valued: Face value of the first $26 of hosted model credits. No period normalization is shown because public evidence does not state an expiration.
Limits and terms
- Signup Model Credit USD
- 26
- Recurrence
- No
- Expiry
- not published
- Platform Layer Free Through
- 2,026
What happens to your prompts?
Ramp-side content recording is enabled by default; inputs, outputs, and tool calls can be retained for one year and used for semantic analysis and product improvement.
- Plan Scope
- Ramp Router trial and routed model traffic.
- Prompt Retention
- Content recording is enabled by default, and recorded request inputs are retained for one year.
- Response Retention
- Recorded outputs and tool calls are retained for one year.
- Ordinary Logging
- Ramp Router retains request and routing metadata even when content recording is disabled; its FAQ does not publish a single deletion TTL for all metadata.
- Model Training
- The reviewed Router FAQ does not establish a blanket no-training promise for every routed upstream.
- Product Improvement
- Ramp may use recorded inputs, outputs, tool calls, and derived semantic information to improve Router; it says personally identifiable information is removed before improvement use.
- Human Or Operator Access
- Recorded traffic is available within Router's operational and improvement systems; the public FAQ does not enumerate role-level human-access controls.
- Subprocessors And Routing
- Router forwards requests to the selected model provider and applies its own recording and routing layer; upstream-provider handling can also apply.
- Deletion Controls
- Disabling recording applies to future requests only after asynchronous propagation and does not delete existing archives. The reviewed FAQ does not describe a self-service retroactive content-deletion control.
- Caveat
- Content capture is on by default, opt-out is prospective, existing archives remain, and recorded inputs, outputs, and tool calls can persist for one year; keep the not private classification.
No provider terms or privacy-policy link is captured in this snapshot. Review the provider’s current legal documents before sending sensitive data.
Eligibility
- Account Required
- Yes
- Us Only
- Yes
- Ramp Card Company Or Llc Required
- No
- Generic Payment Method Required
- not verified
Primary sources
Before you build with Ramp Router
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every region.
Resolve the live model route
No stable model ID is recorded. The offer may use a dynamic catalog, a provider-selected route, or a model class, so resolve the current machine-readable ID before writing a fixed production configuration. The recorded base endpoint is https://api.router.com/v1, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Not private”: Ramp-side content recording is enabled by default; inputs, outputs, and tool calls can be retained for one year and used for semantic analysis and product improvement. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 3 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.