QUICKSTART · DROP-IN · ≈60 SECONDS

OpenAI-compatible. Eleven frontier models. List price halved.

SLASHED is a unified OpenAI-compatible gateway across Anthropic, Google, and OpenAI. Same SDKs. Same response shape. One endpoint. Half the direct-list per-token rate. This page is the shortest path from "never heard of it" to "first call complete".

FIRST CALL · BASH
# 1. point any OpenAI client at SLASHED
export OPENAI_BASE_URL="https://api.slashed.pro/v1"
export OPENAI_API_KEY="sl-..."   # generate at dashboard.slashed.pro

# 2. first call — identical to the OpenAI API
curl $OPENAI_BASE_URL/chat/completions \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.4",
    "messages": [{"role":"user","content":"ping"}]
  }'
— 30-second proof · 01

Eleven models, one endpoint

The full list is public, machine-readable, and unchanged between the dashboard, the SDK, and your billing.

api.slashed.pro/v1/models →
— 30-second proof · 02

Rate card · half of direct list

Every model on the catalogue is published-rate × 0.5, with the upstream provider's official rate in line-through next to it.

slashed.pro/pricing →
— 30-second proof · 03

One-line migration from any OpenAI-compatible gateway

Swap OPENAI_BASE_URL, swap the key prefix, ship. Same SDK, same response shape, half the rate.

Read the migration guide →
— Integration · three steps · ≈60 seconds

From "never heard of it" to first call. Three steps.

Every step below is the actual flow — no marketing detour, no SSO mandate, no calendar invite. If you already have an OpenAI client somewhere in your stack, you're 90 % of the way there.

  1. 01

    Generate an sl- key

    Email-only sign-up at dashboard.slashed.pro. No card, no SSO mandate. You receive a key prefixed sl- plus a 1 M-token migration credit on first issue. The key is scoped per-seat — you can mint sub-keys with their own per-month cost ceilings before you write a single line.

  2. 02

    Point OPENAI_BASE_URL at SLASHED

    Three OpenAI-compatible clients, three near-identical patches. The only thing that changes is the base URL and the key prefix; the model name, message shape, and response shape stay where they were.

    from openai import OpenAI
    
    client = OpenAI(
      base_url="https://api.slashed.pro/v1",
      api_key="sl-...",
    )
    resp = client.chat.completions.create(
      model="gpt-5.4",
      messages=[{"role": "user", "content": "ping"}],
    )
    print(resp.choices[0].message.content)
    from langchain_openai import ChatOpenAI
    
    llm = ChatOpenAI(
      base_url="https://api.slashed.pro/v1",
      api_key="sl-...",
      model="claude-opus-4-7",
    )
    print(llm.invoke("ping").content)
    // app/ai.ts
    import { createOpenAI } from "@ai-sdk/openai";
    import { generateText } from "ai";
    
    const slashed = createOpenAI({
      baseURL: "https://api.slashed.pro/v1",
      apiKey:  process.env.SLASHED_API_KEY,  // sl-...
    });
    
    const { text } = await generateText({
      model: slashed("gemini-3.5-flash"),
      prompt: "ping",
    });
  3. 03

    Make your first call — and read the response

    Copy-paste this. If it returns a non-null content string, you are integrated. The response shape is the OpenAI chat.completions object verbatim — every existing parser keeps working.

    — Request
    curl $OPENAI_BASE_URL/chat/completions \
      -H "Authorization: Bearer $OPENAI_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "model": "claude-opus-4-7",
        "messages": [{"role":"user","content":"In one word: ping."}]
      }'
    — Response (shape, abbreviated)
    {
      "id": "chatcmpl-...",
      "object": "chat.completion",
      "model": "claude-opus-4-7",
      "choices": [{
        "index": 0,
        "message": { "role": "assistant", "content": "pong" },
        "finish_reason": "stop"
      }],
      "usage": { "prompt_tokens": 8, "completion_tokens": 1, "total_tokens": 9 }
    }
— Decision panel · 11 models grouped by job

Which model should I use?

The eleven public IDs at api.slashed.pro/v1/models, grouped by what they're best at. Prices below are per 1 M output tokens; line-through is the direct provider list, bold-accent is the SLASHED rate.

— ICP · DEV / CODING

Code, refactors, diffs

Use when a long-context coding agent has to read a real repo and emit unified diffs without losing the thread.

gpt-5.3-codex$5.00$2.50
claude-sonnet-4-6$3.00$1.50
— ICP · REASONING

Heavy reasoning & analysis

Use when the task is a long-context plan, a board-ready synthesis, or a multi-step research run.

claude-opus-4-7$15.00$7.50
gemini-3.1-pro-preview$3.50$1.75
gpt-5.5$5.00$2.50
— ICP · CFO / SUMMARY

Fast summary, structured

Use when a long document needs to come back as a 12-line summary — fast, cheap, JSON-shaped.

gemini-3.5-flash$0.30$0.15
claude-sonnet-4-6$3.00$1.50
— ICP · BULK / CHEAP

Bulk & high-volume traffic

Use when the cost per call dominates the project — embeddings backfills, batch classification, eval grading.

gemini-3-flash-preview$0.075$0.038
gpt-5.4-mini$1.20$0.60
gemini-2.5-pro$2.50$1.25

Eleven IDs total — gpt-5.5, gpt-5.4, gpt-5.4-mini, gpt-5.3-codex, gpt-5.2, claude-opus-4-7, claude-sonnet-4-6, gemini-3.1-pro-preview, gemini-3.5-flash, gemini-3-flash-preview, gemini-2.5-pro. Full per-token table, input and output, at slashed.pro/pricing.

— Compliance · what you don't have to worry about

Three things that won't happen.

Every claim below traces to a specific contract in the public OpenAPI spec.

Hidden token taxes

SLASHED forwards exactly what your client sent, byte-for-byte, and bills exactly what the upstream reports. No router-authored preamble, no silent system prompt, no platform context on the invoice. See OpenAPI spec →

Silent empty completions

If the upstream returns an error, SLASHED surfaces the error code. We do not return a 200 with an empty completion and silently bill the prompt tokens. See error contract →

Pseudo-model duplicates

Each model has one public ID and one public price. Capability controls are parameters, not duplicate SKUs with separate billing treatment. Verify the list →

— Next stops

Where to go next.

If you got through Step 03 above and it worked, you're done — close the tab. Everything below is reference for the rest of the team.

OpenAPI: api.slashed.pro/openapi.json Models: api.slashed.pro/v1/models Status: status.slashed.pro Privacy /privacy · Terms /terms (DRAFT) Contact: /contact