Drop-in OpenAI-compatible gateway to frontier models from OpenAI, Anthropic, and Google. Same code. Same SDKs. Half the per-token list price.
One endpoint. One rate card. Half the bill.
One base_url swap. Keep your SDK, keep your code. cURL-friendly. OpenAI-compatible. Zero new abstractions.
Real-time spend, per-key caps, per-seat ceilings, single invoice. See the line item drop the moment you switch.
→ dashboard.slashed.proEvery plan accesses the same published per-token rate card at exactly 50% under direct list. What varies is commercial terms (annual vs monthly), procurement options (DPA / BAA / self-host), and engagement model (founder-direct vs founder-introduced).
$0 · 1M tokens to migrate
50% off published direct rate · monthly card billing
Annual · quarterly invoicing · NET-30
All three plans hit the same per-token rate card · only commercial terms differ. The discount isn't tiered; the engagement model is. See the rate card →
Opus is in. Codex Max is in. Codex 5.5 is in. Same response shape. Half the per-token list rate, every call. See the rate card →
A unified gateway across Anthropic, Google, and OpenAI — not the headline, the plumbing. One OpenAI-compatible endpoint. One canonical ID per model. Half the list rate. OpenAPI spec →
// Prices per 1M OUTPUT tokens, USD. Last updated 2026-05-23. Each SLASHED price = provider direct list × 0.5. Verify at anthropic.com/pricing, openai.com/api/pricing, ai.google.dev/gemini-api/docs/pricing. Checked dates and per-model source URLs available on request via hi@slashed.pro.
If your code talks to OpenAI, it already talks to SLASHED. Change the URL. Change the key prefix. Keep everything else.
# Paying direct list rate from openai import OpenAI client = OpenAI( base_url="https://api.openai.com/v1", api_key="sk-...", ) client.chat.completions.create( model="gpt-5.4", messages=[...] )
# Half the bill, same call from openai import OpenAI client = OpenAI( base_url="https://api.slashed.pro/v1", api_key="sl-...", ) client.chat.completions.create( model="gpt-5.4", messages=[...] )
Full reference at api.slashed.pro/openapi.json — endpoints, error codes, rate limits, every supported model ID.
— Also migrating from Quatarly?
# Running on Quatarly client = OpenAI( base_url="https://api.quatarly.cloud/v1", api_key="qua-...", )
# Same SDK. Half the list bill. Real receipts. client = OpenAI( base_url="https://api.slashed.pro/v1", api_key="sl-...", )
Three changed lines either way. OpenAI direct or Quatarly — both migrate to SLASHED with the same gesture.
Same OpenAI-compatible spec. We just didn't break it. Six gateway behaviours observed against their published endpoint — request/response captures and reproduction steps are available on request via hi@slashed.pro.
gpt-5.1 returns content:nullcontent:null for gpt-5.1 — no error, just an empty completion. The failure is invisible upstream; the debug bill is yours.content:null completions are treated as gateway failures, not customer-facing success. We page on it.gemini-3.1-pro-low / -highreasoning, not contentreasoning. Your client crashes. You add a try/catch. You move on.content field. reasoning never becomes an undocumented substitute for the customer-visible answer. Boring is a feature.502 Bad Gateway. Your retry loop hammers them. You can't tell their bug from yours.400 client errors. Upstream 5xx codes are reserved for actual upstream failures. Your retry, alerting, and incident logic just works.Half the list bill. All the receipts.
qua- key →
— Mirror your 30-day usage against the SLASHED rate card. No card. No phone call.
The primary technical liability of any gateway is overhead. We mitigate it structurally: single-hop routing directly to provider endpoints, zero proxy chaining, no tier-based queueing. You incur raw upstream API latency plus network transit — nothing else.
// Third-party benchmarks not yet published. Self-host if you need to measure overhead inside your own VPC.
Works with Claude Code, Codex, Cursor, Factory Droid, OpenCode, raw OpenAI SDKs. Zero vendor abstractions to learn.
TLS 1.3 in transit. Prompts and completions live only as long as the request. No retention, no training, no leaks.
Live token counter, per-key caps, per-seat ceilings, daily digests. The dashboard mirrors the API, line for line.
Email hits engineers who read traces and ship fixes — no ticket maze, no tier-1 hand-off. Not vibes. Not vanished threads.
For buyers whose data residency, sovereignty, or compliance posture cannot accommodate a third-party gateway in the request path. Same routing intelligence, deployed inside your cloud (or on-prem). Same dashboard. Your audit trail, end to end.
AWS, GCP, Azure, or on-prem. Terraform + Helm chart provided. Single-region default; multi-region available on request.
The same lane-selection logic and provider-failover policies that run on slashed.pro/v1, deployed under your DNS, behind your VPC, with your existing IAM controls.
Every request logged locally to your S3 / GCS / Blob. No cross-tenant log mixing. Full export to JSON or CSV; retention configurable per-engagement.
No per-token rate. Predictable annual contract priced against your forecast volume. Quarterly invoicing. NET-30. Standard commercial terms.
The 50% direct-list savings still applies via your own pass-through provider credentials. Provider keys (Anthropic, OpenAI, Google) stay yours. We never see traffic in this deployment.
Talk to a founder about self-hosting →Mature buyers deserve a cold, declarative manifest — not a privacy-policy PDF buried three clicks deep. Here it is, in one block, in monospace.
// ENCRYPTION: TLS 1.3 in transit; AES-256 at rest. // RETENTION: Zero. Payloads exist strictly for request duration. // TRAINING: Zero. We never inspect or train on customer prompts or completions. // COMPLIANCE: SOC 2 Type II [audit in progress · target Q4 2026]. // RESIDENCY: US-East default. Multi-region routing on request. // ISOLATION: Per-key rate limits, per-key audit logs, cryptographic key separation.
If a procurement form needs a paragraph instead of a block, write to hi@slashed.pro — a founder replies, not a queue.
— RFP-grade summary · six requirements, evidence-pointed
content field is canonical.For finance leads who cannot expense card payments and need the savings on a procurement schedule — the same 50% list discount, packaged as a quarterly bill.
-low/-high tier splits inflating SKU count. Models on the invoice equal products consumed.400, not 502. Retry-loop spend stays bounded, not amplified.Connect any sl-, qua-, sk-, or or- key. The dashboard imports your last 30 days of usage and projects what the same workload would have cost at direct list. CFO-shareable. Audit-trail clean.
— Begin · free 1M tokens to migrate · no card
Get your sl- key →