The platform(opens the documentation in a new tab)

Call any provider through api.nemu.cc.

api.nemu.cc speaks chat completions, the Responses API and Anthropic Messages, and serves any of them from any provider you connect. The console decides which model answers, what it may spend, and keeps a record of every call.

Free to start. Bring a key from a provider you already use.

basehttps://api.nemu.cc
  • Chat completionsPOST /v1/chat/completions
  • ResponsesPOST /v1/responses
  • Anthropic MessagesPOST /anthropic/v1/messages
Protocols(opens the documentation in a new tab)

The gateway translates protocols in both directions.

The URL picks the protocol you speak. The provider's compatibility setting picks the one spoken upstream. System blocks, tool calls, streaming events, thinking and cache breakpoints are converted in both directions.

Hosted tools such as web search and code execution pass through only from an Anthropic client to an Anthropic provider.

Chat completionsResponsesAnthropic Messages
Providers(opens the documentation in a new tab)

Your provider bills the tokens at the rates you already pay.

Every call runs on the provider key you added in the console, so OpenAI, Anthropic or whichever provider you connected bills the tokens directly. nemu adds no markup. Credits pay only for the Computer, web search, page reads and deep search.

  • Any provider, or your own server

    Pick a service from the catalog, or point at your own https endpoint: a local server, a private deployment, a proxy.

  • Metrics show the cost of each call

    Each row records what the call cost at your provider's price, so you can check the bill before it arrives.

  • Provider errors are labeled

    When your provider account runs out of funds, the 402 response says it came from the provider. Top up with the provider; nemu credits are not involved.

  • The gateway works on Free

    The Free plan has no credit balance, and the gateway still serves 3,000 requests a month on it.

Routing(opens the documentation in a new tab)

Change which model answers without a deploy.

Your code keeps sending the same name. The console decides what that name means today, and Metrics records the model that actually answered.

  • Rename the model a client asks for before anything else runs, so code with a hardcoded model name uses the model you chose.

    gpt-4oanthropic/fable-5.1

  • A small graph that picks the model at call time from your own usage, the time of day or whether the request carries an image.

    openai/gpt-4oopenai/gpt-4o-mini

Spend on openai/gpt-4o, last 7 days

The client asked for openai/gpt-4o. It runs on openai/gpt-4o, and Metrics records the model that actually answered.

Coding agents(opens the documentation in a new tab)

Run Claude Code and Codex on any model you enable.

Claude Code speaks Anthropic Messages and Codex speaks the Responses API. Both are served for every model you enable, so an agent built for one provider runs on another. Point either one at the gateway with a base URL and a key.

~/.claude/settings.json
{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.nemu.cc/anthropic",
    "ANTHROPIC_AUTH_TOKEN": "YOUR_NEMU_GATEWAY_KEY",
    "CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY": "1"
  }
}
Plans(opens the documentation in a new tab)

Mappings and workflows are on every plan, including Free.

On the Free plan

  • 3providers
  • 5models
  • 3mappings
  • 5prompts
  • 2quota rules
  • 3workflows
  • 2workspaces
  • 3,000requests a month
  • Limits count per account. Ten keys share one allowance rather than getting ten.
  • When a plan lapses nothing is deleted. Anything above the new limits stops taking new work until you are back under them.

Send one request, then open Metrics.

Connect a provider, enable a model and create a key. The quickstart takes about five minutes, and your first request shows up in Metrics as soon as it completes.

$ curl https://api.nemu.cc/v1/models -H "Authorization: Bearer $NEMU_KEY"