Agent-native infrastructure
Infrastructure your agent can actually buy.
Domains, authoritative DNS, a free private git repo, and push-to-deploy hosting behind one API token an agent gets in its first second. No signup form. No CAPTCHA. No browser handoff. You appear exactly once — at a payment link in your inbox.
$ curl -sX POST https://api.slipdock.ai/v1/workspaces \ -d '{"owner_email":"you@example.com"}' {"workspace_id":"ws_7f3a","token":"sk_live_...","plan":"free"} # one call. no form, no CAPTCHA, no browser, no card. $ curl -s https://api.slipdock.ai/v1/repos -H "$AUTH" \ -d '{"name":"my-app"}' {"clone_url":"https://git.slipdock.ai/ws_7f3a/my-app.git"} # private git repo, free, no human involved $ git push slipdock main → built, deployed, serving on https://my-app.slipdock.app $ curl -s https://api.slipdock.ai/v1/domains/register -H "$AUTH" \ -d '{"domain":"example.com"}' 402 payment_required — pay-link emailed to you@example.com next_action: await_payment · poll /v1/orders/o_1f2e # this is the only step an agent cannot do. by design.
The rule that makes this safe to install
An agent can do everything here except move money. That is not a limitation we engineered around. It is the trust architecture, it is checked in exactly one function on the server, and it is the reason you can hand an autonomous agent a token at all.
Searches domains, claims a repo, pushes code, deploys, writes DNS, reads the ledger, renews, reports runway.
Approves the payment. Sets the spending cap. Nothing else is required of you, and nothing spends without you.
Every provider in this market puts a human-shaped wall in front of an agent — an account signup, a card form, a CAPTCHA, a dashboard. Slipdock keeps exactly one of those walls, puts it around money only, and removes the rest.
What an agent gets before any money exists
The free plan is not a trial with a countdown. It is the thing the agent receives in its first minute, so its first success needs no human at all.
A private git repository
100 MB, private, yours. git push is the one deploy
transport every agent already has — almost none can build and push an OCI
image. It is a plain git remote: clone it and leave whenever you want.
An app, actually running
Push source, we build it and serve it. One app and one static site on the free plan, scale-to-zero, HTTPS included.
Authoritative DNS
Full record CRUD on zones in the workspace. DNS costs us almost nothing, so it is free and it is not payment-gated.
Unlimited domain search
Availability and a firm price for every supported TLD, cached, with no payment method anywhere in the account.
The one human moment
waiting for you
An email arrives with a line-item total and one button. You approve it. That is the entire human interface to Slipdock.
On that same page you can add credit and set a per-purchase cap. After that your agent buys inside the cap on its own, and anything larger comes back to you exactly like this. You can empty or revoke the wallet at any time, and running low warns you at 30 days of runway — not at zero.
Slipdock does not store a card on file and then hope the agent behaves. There is no card on file. There is a balance a human put there and a ceiling a human chose.
One token across the whole stack
An agent shipping a real service today juggles four or five accounts and four or five payment gates: a registrar, a DNS host, a git host, somewhere to run the thing, a database. Each one wants to be the destination. Slipdock wants to be the token.
| Resource | Endpoint | Costs money? |
|---|---|---|
| Domain search | GET /v1/domains/search | free |
| Domain registration | POST /v1/domains/register | yes — human approves |
| Authoritative DNS | POST /v1/dns/{zone}/records | free |
| Private git repo | POST /v1/repos | free |
| Static site | POST /v1/static | free tier |
| Deployed app | POST /v1/apps | free tier, then a paid plan |
| Managed Postgres | POST /v1/apps (database plan) | paid plan |
| Wallet and ledger | GET /v1/wallet | free |
…and leaving stays easy
An aggregator accrues switching cost naturally. Once your domain, code, DNS and database live in one place, moving means re-integrating four things — that gravity is earned. Friction is not. Every one of those things exports, in a standard format, at any time, for no fee.
How you take each thing with you
- Repo — a plain git remote.
git clone. - Database —
pg_dump, whenever you like. - DNS zone — a standard zone file.
- Domain — transfer auth code on request, no fee and no hold beyond the one ICANN requires.
- Billing history — the full ledger, exportable.
And what we will not do
- No export fee and no "contact sales" to get your data.
- No degraded export that technically satisfies the promise.
- No retention flow on cancel — the same token that created a subscription cancels it.
- Export still works while a workspace is suspended for non-payment. Data is never the hostage.
Built to be read by a machine
Errors say what to do next
Every non-2xx carries a next_action object — poll this
URL, retry with that field, ask the owner. An agent should never have to
guess, and guessing is where agent loops burn money.
Three views, one surface
REST, an MCP server, and llms.txt describe the same nouns. OpenAPI is generated from the implementation, not written beside it.
Nothing needs JavaScript
Not this site, not the pay page, not the docs. Turn JS off and everything still reads. A headless fetch gets the whole thing.
Domains at cost, on purpose
We sell .com at $10.44 — Cloudflare's at-cost price, and about $1.06 below what the domain costs us. Same for .org, .net. We would rather tell you that than dress up a loss as a discount.
The money is in hosting, databases and the wallet. If the domains are the only thing you ever buy from us, we lose money on you, and that is a deliberate bet — not a secret.
Common questions
Does an AI agent need an account to use Slipdock?
No. One POST /v1/workspaces with the owner's email address returns a workspace and a scoped API token immediately. There is no password, no CAPTCHA, no email confirmation loop and no browser step. The human never signs up; they appear once, at a payment link, and only if something costs money.
How does an agent pay for anything if it cannot move money?
It doesn't. The agent creates an order. Slipdock emails the workspace owner a payment link, returns HTTP 402 with a next_action telling the agent to poll, and the agent waits. Once the human approves, the order flips to complete and provisioning runs. If the owner has funded a wallet and set a per-purchase cap, purchases inside that cap complete immediately with no email — because a human already authorised that amount.
What can an agent get with no payment at all?
A private git repository, one deployed app, one static site, authoritative DNS records for domains in the workspace, and unlimited domain availability searches. All of it on the free plan, all of it before any payment method exists anywhere in the account.
What stops an agent overspending?
A wallet cap the human sets, enforced in exactly one function on the server. Anything above the cap goes back to email approval. Free-plan quotas behave the same way in the other direction: exceed them and the app throttles rather than generating a bill nobody agreed to.
Is Slipdock cheaper than Cloudflare for domains?
No — the same. We match Cloudflare's at-cost price on the popular TLDs, which for .com means $10.44, about a dollar below what the domain costs us. Domains are the hook, not the business; hosting and databases are where the margin is, and we would rather say that than pretend otherwise.
Is any of this live yet?
Partly, and honestly: the control plane runs end to end in staging — instant token, free private repo, git push build, a live app serving traffic, DNS records resolving, quota enforcement, domain search against the registrar sandbox. It is not production. State is still ephemeral, the second nameserver does not exist, public DNS delegation is not done, the pay-link does not yet take a card, and abuse screening is not built. There are no customers. The full list is on the about page.