Skip to content

Every endpoint,
a tool agents can call.

Give Sokie an OpenAPI, Swagger or GraphQL spec. Each endpoint becomes a typed tool on a live MCP server at its own address.

Start building

Press and hold the ground, or drag through it. Point at a client to see what it calls.

Our own apps run on Sokie

  • TakeOne
  • Antescript
  • Gatherd
  • Latem
  • Sokie

Four commands from a spec to a server people can call.

Run them here, on a sample billing API. Each does to it what it would do to yours.

~/billingzsh

$

Or pick any command above.

What it writes

your repository
openapi.yamltools/
Run sokie init to write the tools.

Each tool is a Markdown file you own: its description, its risk, the operation it calls. Edit one and the server changes; nothing is generated code.

Big APIs stay small
Past 40 operations, a server offers agents three tools: one to search the rest, one to read a tool, one to call it. Hundreds of tools never crowd an agent’s context.
Every tool says what it can do
Read, write, delete, or an effect outside the API, like sending an email. Clients use it to decide when to ask you first.
Both versions of MCP
Every server speaks MCP v2 (the 2026-07-28 spec) and still answers clients on the 2025 one.

The billing API, its tools, the responses and the address are a sample.

Or skip the terminal. Paste a URL.

The New server page reads your spec, lets you choose the tools, and deploys. Swagger’s Petstore went from its address to a live server in under a minute. No spec to hand? Try the sample weather API from your Dashboard.

Spec address: https://petstore3.swagger.io/api/v3/openapi.json
  1. Step 1, done: SourcePaste the spec’s address, upload it, or pick a repository.
  2. Step 2, done: Tools19 operations become 19 tools. Leave some out, edit what agents read.
  3. Step 3, done: Name and accessPrivate by default: clients sign in to Sokie first.
Live in under a minutepetstore.sokie.cloud/mcp

The address is a sample.

Every pull request gets its own server.

Link a GitHub repository and pushes deploy. A pull request gets a preview at its own address, rebuilt on every push and gone when it closes.

Bring your own agent. Buy no AI credits.

When a server needs AI work, like better descriptions, tests or a fix for a failed deploy, Sokie hands it to Wake. Wake starts your own coding agent on your machine, in the right repository, in a sandbox on its own branch. It opens a pull request; you review it.

Your agent
  1. SokieAsk my agentYou ask from the server's page. No model runs on Sokie, and none is billed.
  2. Your machineWake
    $ wake
    ● waiting for work
    Wake starts Claude Code where your code lives: sandboxed, on its own branch.
  3. GitHubPull requestNo pull request yetwaiting for workThe work arrives as a pull request, with a preview to try before you merge.
AI credits compared with your own agent through Wake
Compared onAI credits elsewhereYour agent through Wake
The modelthe platform's pickClaude Code, yours
Who pays for itcredits you buythe subscription you have
Where the code runstheir machinesyours, in a sandbox

Your keys stay yours.

Every client signs in with OAuth before its first call, and you allow each one. Secrets and each caller’s own key are encrypted and never shown again. Logs keep what happened, never what was sent.

How Sokie keeps your API safe

Priced on hosting. Never on AI.

Start free with no card. Plans grow with who connects to your servers. Who will?

Who connects to your servers
Plans

AI credits are $0 on every plan. Each caller can make 120 requests a minute and 20,000 a day to a server. Every limit

One line on your bill is always zero.

Sokie charges for the servers it runs. The AI work is your agent's, on the subscription you already pay for, so there is nothing to top up.

Start building