---
title: "Ramp Router free inference"
description: "$26 for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Ramp Router."
canonical_url: "https://freeinferencing.com/provider/ramp_router/"
md_url: "https://freeinferencing.com/provider/ramp_router.md"
last_updated: "2026-09-19"
---

# Ramp Router

> $26 for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Current trial
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** $26.00 once
- **API endpoint:** `https://api.router.com/v1`

## Models mentioned

No stable model IDs were recorded in this snapshot.

## Limits and terms

```yaml
signup_model_credit_usd: 26
recurrence: false
expiry: not_published
platform_layer_free_through: 2026
```

## What happens to your prompts?

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

Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data.

## Data governance and agreements

```yaml
data_governance:
  review_status: reviewed
  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.
```

## Eligibility

```yaml
account_required: true
us_only: true
ramp_card_company_or_llc_required: false
generic_payment_method_required: not_verified
```

## API compatibility and modalities

- **Compatibility:** OpenAI Compatible, Anthropic Compatible
- **Modalities:** Model inference
- **Geography:** United States

## Before you build with Ramp Router

### Read the classification narrowly

This record 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 account and region. “One-time trial” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below.

### Resolve the live model route

No stable model ID is recorded. Resolve the current machine-readable ID, endpoint, authentication method, and request shape from the provider's live documentation before writing fixed production configuration.

### Match the quota to the workload shape

Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms.

### Preserve billing and privacy boundaries

The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Not private** because 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. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content.

### Follow the evidence, then re-check it

This record links 3 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term.

### Plan fallback without policy drift

A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable.

### Monitor the offer as a dependency

Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity.

### Test one complete request before scaling

Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement.

## Primary sources

- [Ramp Router](https://router.com/): Official Product
- [Endpoint](https://docs.router.com/api/endpoint): Official API Reference
- [Frequently asked questions](https://docs.router.com/resources/faq): Official Docs

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.