All articles

Developers3 min read

Your editor, minus your name

Point the editor, terminal tool or chat app you already use at Moth, and the model still reads your code, but nothing on the request says it came from you.

What your editor sends

Your editor already talks to a model. It sends the file you have open, the error you just hit and a page of its own instructions, all under a key with your name on it.

The host that answers sees every one of those calls arrive from the same account and the same network, day after day. Over a few weeks that adds up to a clear picture of what you build and how you work.

Figure 1. What a request carries, before and after the MothpointFive fields leave your laptop. Four of them say who you are, and none of those reaches the host as you sent it.
says who you areremovedgoes on

As it leaves your laptop

Mothpoint

As the host receives it

Account keynames you
Pooled keyshared by every caller
IP addresslocates you
IP addressMoth's server, not yours
User agentdescribes your device
User agentremoved
User fieldoften set by the app
User fieldremoved
Promptthe question
Promptthe question

What changes on Moth

Point the same editor at Moth and your code still arrives, because the model needs it to answer. What no longer arrives is you.

Your account, your IP address and your key come off at the Mothpoint, and the call goes on under a key shared by everyone who uses Moth. The host reads the question and has no way to tell whose it was. Nothing you send is written down on our side, apart from one billing row for each call.

The model still reads your code. It just can't tell the code was yours.

Everything else stays where you left it. The tool keeps its shortcuts, its context and its habits, because all that moved is the address it calls and the key it carries.

One key for each tool

Every tool draws on the same balance, so there is one top-up for all of them instead of a bill from each maker. Give each tool a key of its own, though, and Moth Console can keep them apart.

Figure 2. Five makers, two ways to pay themFive makers usually mean five accounts, five keys and five bills. On Moth the same models sit behind one key and one balance.

Todayone account, one key and one bill per maker

  • Anthropicaccountkeybill
  • Googleaccountkeybill
  • OpenAIaccountkeybill
  • xAIaccountkeybill
  • Kuaishouaccountkeybill

With Mothone balance and one key for every maker

one moth_ keyone balance
  • Anthropicbelow list
  • Googlebelow list
  • OpenAIbelow list
  • xAIbelow list
  • Kuaishoubelow list
  • A cap on each key. An agent that loops overnight stops at the cap you set for it, and the rest of your balance stays put.
  • A line for each key in Logs. Every call shows which key made it, what it cost and how long it took, so you can see what each tool spends.
  • Revoke one, keep the rest. If a key ends up somewhere it shouldn't, revoke it and every other tool carries on.

Where it works today

Any tool that lets you set its own base URL can reach Moth. These have a page each in the docs, with the setup as each tool asks for it today.

  • Editors and agents. Cline, Continue and Zed work with any chat model that can call tools, and Aider with any chat model. Cursor sends its chat to Moth, while its Tab completions stay on Cursor's own models.
  • Chat apps you host. Open WebUI and LibreChat list every Moth chat model once they have one connection.
  • Your own code. The Vercel AI SDK and LangChain take Moth as a provider, and so does any OpenAI or Anthropic SDK.
9
tools with a setup page in the docs
2
request formats taken, OpenAI's and Anthropic's
19
chat models behind one key

What Moth can't change

  • What a prompt says. A file that holds a password still holds it on the way to the model. Turn on Shield for a key, and API keys, emails, card numbers and wallet addresses leave Moth as placeholders and come back filled in.
  • What a tool does first. Cursor builds every prompt on its own servers before it reaches Moth, so Cursor sees it. Moth's promise starts where a tool hands the request over.
  • Tools that need another API. Claude Code and OpenAI's Codex CLI don't work with Moth yet, because each needs parts of an API that Moth doesn't serve today.

Set one up

Aider takes two lines in a terminal and a model name.

Aidershell
export OPENAI_API_BASE=https://api.runmoth.si/v1
export OPENAI_API_KEY=$MOTH_API_KEY
aider --model openai/claude-sonnet-4.6

Zed takes one block in its settings, and reads the key from MOTH_API_KEY.

Zed, settings.jsonjson
{
  "language_models": {
    "openai_compatible": {
      "Moth": {
        "api_url": "https://api.runmoth.si/v1",
        "available_models": [{ "name": "claude-sonnet-4.6", "max_tokens": 200000 }]
      }
    }
  }
}

Make a key in Moth Console and pick your tool in the Tutorials. Your first call shows in Logs a few seconds later, with what it cost.

Read further