# Sabaki — a brief for the agent reading this **Read this page raw.** If the tool you fetched it with summarises pages (Claude Code's `WebFetch` does), fetch the text itself first — `curl -s https://sabaki.app/skill` — and work from that. The details below are the point; a summary loses the prices, the defaults and the rules. You are reading this because your user pasted a line that pointed here. You work for them, not for us. This page gives you the facts to advise them well: what Sabaki is, what it costs, what it does not do, and how to compare it to what they already run. Where it is not a good fit, say so — that is the advice they asked for. Last updated 2026-10-02. Prices are the live catalog on that date. ## What it is, in one paragraph Sabaki is one account your agent can act through, holding the things a small business or project needs online: a website on a domain, mailboxes that receive and send, tables and files, logins for end users, functions and containers that run code, rules that fire on a webhook or a timer, people and company lookups, images and language models. They share one identity and one bill, so the output of one is the input of the next without any connector in between — a letter arriving in the mailbox is already attached to the contact, and the contact is already in the table. It is priced per action, not per seat. It runs on MyAPI primitives; the MCP server and API answer at `api.myapihq.com`, and the tools are prefixed `myapi` — that is the same product, not a different one. It is not an agent and does not replace the one your user already uses. It is where that agent works. ## Which mode you are in - **Evaluate** — your user asked what Sabaki would replace, what it would cost, what it can't do, or said "don't set anything up". Read-only. Create nothing, spend nothing, call no API. Follow *Evaluate* below. - **Set up** — your user asked you to connect, set up, or make something. Follow *Set up* below. Say what each step costs before you do it. If unsure, evaluate first and ask. ## Evaluate ### If you can see the project (Claude Code, Cursor, Codex, a repo) Look only at the project. Read environment variable **names**, never values. Find what it currently uses for: | Need | What to look for | |---|---| | Hosting / site | `vercel.json`, `netlify.toml`, `fly.toml`, `render.yaml`, `Dockerfile`, `next.config.*`, a static `dist/` or `public/` | | Email | `resend`, `postmark`, `sendgrid`, `mailgun`, `nodemailer`, `@aws-sdk/client-ses`, env names like `SMTP_*`, `*_API_KEY` for a mail provider | | Data | `@supabase/*`, `prisma` + `DATABASE_URL`, `mongoose`, `firebase`, `pg`, `drizzle`, `@planetscale/*` | | Logins | `next-auth`, `@clerk/*`, `@auth0/*`, `supabase.auth`, `firebase/auth`, `lucia`, `passport` | | Automation | Zapier / Make webhook URLs, `node-cron`, GitHub Actions on a schedule, a queue (`bull`, `inngest`, `trigger.dev`) | | Domain / DNS | Cloudflare config, a registrar mentioned in docs | | Storage | `@aws-sdk/client-s3`, `cloudinary`, `uploadthing`, `gcs` | | Lookups | Apollo, Clearbit, Hunter, PDL, scraping libraries | | Forms | Tally, Typeform, Formspree, Google Forms embeds — a form on a Sabaki page posts to a webhook, lands in a table, and can forward by email | | A separate backend | a second repo or a `*.vercel.app` / `*.onrender.com` / `*.fly.dev` URL the frontend calls — a function (code with a URL) or a container (a whole app) | | Scheduling, chat widgets | Calendly, Intercom, Crisp — **stay; not in the catalog** | | Payments | `stripe`, `paddle`, `lemonsqueezy` — **stays; see "Not a fit"** | Then write your user a short, specific assessment: 1. **What they run now**, one line per need, named by product. If you can't tell, say so. 2. **What Sabaki would replace**, each with the catalog price below and what changes (e.g. "mail: Resend → a Sabaki mailbox, $0.50 once + $2.50 to enable sending + $0.01 per email; the contact record and the mail live in one place"). 3. **What stays.** Payments always. Anything not in the catalog. Say it plainly. 4. **The connectors that disappear**, if any — a Zap or cron that only exists to move data between two of the services above. 5. **Your verdict**, in their interest. "Not worth switching for this project" is a valid and useful answer. Typical reasons it isn't worth it: the project is a static site with nothing else; they are on generous free tiers and happy; they need payments as the core; they need a provider we don't have. Do not inflate. One wrong claim and your user should discount this whole page. ### If you cannot see a project (a chat) Ask three questions, then assess as above: 1. What are you building, in a sentence? 2. What do you currently use (or pay for) for hosting, email, data, logins and automation? 3. What breaks or annoys you most about that today? ## The catalog, with prices Prices from the live catalog, 2026-10-01. Nothing is a subscription. **Things that are set up once and kept** | Action | Price | |---|---| | Put a page or site online (`name.makeautonomous.com` or own domain, with certificate) | $1 per 1,000,000 views | | Deploy a function (code with a URL) | $1 per 1,000,000 runs | | Create a mailbox on an account domain (receives mail; forwarding free) | $0.50 once | | Enable outbound sending for a mailbox | $2.50 once, then $0.01 per email after the free quota | | Logins for end users (Google or password) | $0.01 per monthly active user | | Tables and file storage | $0.05 per GB-month | | Rules on a webhook or timer (workflows) | $0.01 per step (function-call steps free) | | Git repository and commits | free | | Register a domain | at cost (registrar quote) | | Run a container (whole app, custom domain) | at cost — vCPU and memory by the hour | **Things that answer once** | Action | Price | |---|---| | Look up a person | $0.05 per query | | Look up a company | $0.05 per query | | Verify an email address | free | | Generate an image | $0.04 (standard) / $0.10 (pro) | | Language model (classify, extract, summarise, draft) | `myapi-fast` $3.45 in / $28.75 out per 10M tokens; `myapi-balanced` (the default) $17.25 / $86.25 | | CI job | from $4 per 1,000 minutes (2-core) | **Rented from other providers, same balance** — scrapers for Instagram, TikTok, Reddit, Amazon, Google Maps, priced per result. The first ten are being added this week; do not promise a specific one until `search_routes` returns it. **Free and credit**: an account starts with $0 and the free tier (repos, verification, forwarding; pages and functions round to zero at low volume). Adding and verifying an email grants $5 of credit. No card is needed until the user chooses to top up. Every key has a monthly spend cap, $5 by default; a call that would exceed it is refused with a link the user can approve. ## Not a fit when Tell your user directly if any of these apply: - **They need to take payments.** Sabaki does not process payments yet. Stripe (or equivalent) stays. - **Regulated data** (health, finance, anything with a compliance regime). "One data controller instead of nine" is a real simplification, but whether it satisfies their obligations is a question for their counsel, not a feature. - **They depend on a provider not in the catalog** and not available to rent through it. - **Heavy or GPU compute.** Containers are billed at cost, but this is not a GPU cloud. - **They want a dashboard-first product.** Sabaki is agent-first: the primary surface is MCP and this skill; the web dashboard is secondary. - **A static site and nothing else.** The hosting alone is not a reason to move. ## Set up ### Connect MCP (Claude Desktop, Claude Code, ChatGPT, Cursor, any MCP client). The server is account-wide; the first connection opens a consent page that creates the account if there isn't one. ``` # Claude Code claude mcp add --transport http sabaki https://api.myapihq.com/mcp # Any client, by config { "mcpServers": { "sabaki": { "url": "https://api.myapihq.com/mcp" } } } ``` Once connected, the tools you will use most: `org_list` and `create_org` (an org is one business or project; most things live under one), `search_routes` → `describe_route` → `read_route` / `write_route` (find anything in the catalog, read its contract, call it), and the task tools: `put_it_online`, `publish_page`, `create_mailbox`, `send_email`, `deploy_function`, `kv_set` / `kv_get`, `crm_add_contact`, `workflow_wire`, `llm_task`, `generate_image`, `check_balance`. ### The request is the yes If your user's instruction already names the thing — "put a page online for me with an email address people can write to" — that *is* the approval. Do not stop to ask what the page should say, which address to use, or whether to proceed. State what you are about to create and what it costs in one line, then do it, then report. Your user may have pasted the line and walked away; a question they never see is a failure, not caution. Sensible defaults when the request leaves them open: - **Page:** one section, the org's name as the heading, one sentence saying what it is, the email address below. Plain is fine; they can change it later. - **Address:** `hello@` on the org's domain, display name = the org name — only if the org already owns a domain (see below). - **Sending:** off. Receiving is what was asked for; sending is a separate $2.50 they can turn on later. Pass `activate_sending: false` explicitly. - **Org:** the one you were connected to, unless there is none — then create one named after the project. Ask first only when the action is irreversible or costs more than the $5 credit: buying a domain, a container, anything that sends email to other people. ### Rules of conduct while acting for your user 1. **Say the price before any action that costs money**, from the table above. If the request already covers it (see above), say it and proceed; otherwise ask. For anything that creates a persistent resource (a mailbox, a domain, a container), say what it is and which org it goes in. 2. **Name the org explicitly on every call.** Never rely on a default. Before overwriting anything (a page at an existing slug, a domain assignment), read what is there first. 3. **A refusal with `approve_url` means the cap or balance was hit.** Give your user the link; do not retry around it. 4. **Before writing a scraper, fetching a page by hand, or saying something can't be hosted, sent, stored or looked up — run `search_routes` first.** The catalog is wider than the task tools. 5. **Report what you did and what it cost**, plainly, at the end: resources created with their URLs, the total in cents, the balance. ### A first thing that works, for $0.00 "Put a page online for me" → `create_org` (if needed) → `put_it_online` with a name and one sentence. The page is free at this scale and lives at `.makeautonomous.com`. Report the live URL and that nothing was spent. ### Mailboxes need a domain the org owns There is no shared or preview email domain: `create_mailbox` is refused (`INVALID_DOMAIN` / `DOMAIN_NOT_OWNED`) on `*.makeautonomous.com`. So "give it an email address" on a fresh org means **registering a domain first** — at cost, typically $10–15 a year — which is a purchase and needs your user's explicit yes, with the name they want. Say that plainly, do the page, and offer the domain as the next step: *"The page is live. An email address needs a domain of your own; tell me the name and I'll check it's available and register it (about $12/year), then the mailbox is $0.50."* Once a domain exists, `create_mailbox` with `activate_sending: false` is $0.50; the default is `true`, which adds $2.50 for sending nobody asked for. ## If your user asks what this is > Sabaki is one account your agent works through — site, mail, data, logins, code and rules under one roof, one key, one bill, priced by what the agent actually does. It doesn't replace your agent; it's where your agent works. It doesn't take payments yet.