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.
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
GatherdLatem
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.
$
What it writes
your repositoryEach 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.
https://petstore3.swagger.io/api/v3/openapi.json- Step 1, done: SourcePaste the spec’s address, upload it, or pick a repository.
- Step 2, done: Tools19 operations become 19 tools. Leave some out, edit what agents read.
- Step 3, done: Name and accessPrivate by default: clients sign in to Sokie first.
petstore.sokie.cloud/mcpThe 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.
- SokieAsk my agentYou ask from the server's page. No model runs on Sokie, and none is billed.
- Your machineWake
$ wake ● waiting for work
Wake starts Claude Code where your code lives: sandboxed, on its own branch. - GitHubPull requestNo pull request yetwaiting for workThe work arrives as a pull request, with a preview to try before you merge.
| Compared on | AI credits elsewhere | Your agent through Wake |
|---|---|---|
| The model | the platform's pick | Claude Code, yours |
| Who pays for it | credits you buy | the subscription you have |
| Where the code runs | their machines | yours, 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 safePriced on hosting. Never on AI.
Start free with no card. Plans grow with who connects to your servers. Who will?
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