Create, change, and publish whole apps from your own code.
One key, one REST API. Turn a description into a running app with its own database and sign-in, then patch it, publish it, roll it back, and read its logs — all as calls.
curl -X POST https://api.exepad.com/v1/apps \
-H "Authorization: Bearer $EXEPAD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Client intake",
"type": "form",
"description": "A client intake form with an admin dashboard"
}'
# name is required. type is one of website | form | dataapp | custom.
# description is what the build is generated from.
# The response carries the edit that is building it — poll it, stream it,
# or cancel it: GET /v1/edits/{id}, /v1/edits/{id}/stream, /v1/edits/{id}/logsRequires Pro and a funded balance · Published in minutes
See what changes ↓What normally stops you
You can build the app. That was never the question. The question is whether it is worth a week of your life — sign-in, a database, file uploads, transactional email, a publishing path, a domain — for a request queue six people will use twice. So it goes on the backlog. And the builders that could do it in an afternoon are closed editors with no way in from your terminal.
What changes for you
Four things that work differently once you build this way.
From description to running app
Before
A new app means a repo, a schema, an auth layer and a hosting story before a single screen renders.
After
One call creates it from a name and a description. Poll the build, stream it live, or cancel it — and read its logs either way.
Patch the app, not a repo
Before
Changing a generated app means opening its editor and clicking through someone else’s idea of a workflow.
After
List the files and read any of them, then send a replacement in. Or submit a structured change and let the build apply it for you.
Publishing you can undo
Before
Shipping is a one-way door. Something breaks in front of real users and the only fix is another full build.
After
Preview, publish, unpublish. Full version history on the API, and a single call to put an earlier one back.
A key can build; only you can spend
Before
An API key is usually a blank cheque.
After
Keys build, publish and read. Top-ups, payment methods and spending limits need your own signed-in session. Never a key.
The same app, three ways
The same app, three ways in: described, coded, or delegated. You are on the code lane — the other two run against the same platform, and nothing you build here is locked out of them.
People
By describing it
- Describe the site or tool you want, in a sentence or two.
- Read what comes back and ask for changes until it says what you mean.
- Publish it to a live web address and send people the link.
Developers
By writing code
- Start the app from your own code instead of a description.
- Write the parts you care about by hand, and change any file.
- Publish it, watch it, and roll it back if you need to.
Agents
By delegating it
- Hand an agent your key and let it build the app for you.
- It reads the app back, makes the changes you asked for, and publishes.
- Your balance and your spending limits stay yours alone.
The surfaces
Three surfaces over the same platform. One key authenticates your calls on all of them, and every operation bills against your wallet balance.
REST
https://api.exepad.com/v1
Apps, files, edits, publishing, settings, logs, webhooks and billing. Bearer-authenticated JSON; builds stream over SSE.
MCP
https://mcp.exepad.com
26 working tools over JSON-RPC covering the whole lifecycle — create, inspect, edit, publish. Point any MCP-capable client at it.
Webhooks
https://api.exepad.com/v1/webhooks
Subscribe to build and publish events. Full delivery history, a test call, and retry on any single delivery.
What people like you build
Start from a category instead of a blank page.
Internal tools
The request queue, the admin panel, the tracker that never once justified a sprint. Create it in a call and hand it over with its own sign-in already on it.
Customer apps
Accounts, bookings, Stripe checkout, transactional email — generated with the app rather than bolted on after it, and patchable file by file.
But what about…
What do I need before my first call?+
An active Pro subscription and a funded wallet balance, or auto-reload switched on. Mint a key from your account and usage is billed per operation against that balance. There is no free developer tier — the API is a Pro capability, not a trial you can start cold.
What can a leaked key actually do to me?+
It can build, and building costs money. It cannot top up your balance, add or change a payment method, or raise a spending limit — all three require your own signed-in session. So the worst case is bounded by the funds you chose to put in, and you revoke the key.
Can I export the generated code and take it elsewhere?+
No. You can write your own components and send them in, read every file back through the API, and send replacements in — but there is no download or export. If owning a repository you can walk away with is a hard requirement, this is the wrong tool, and we would rather you knew that now than later.
Do my published apps each get an MCP endpoint?+
No. MCP lives at the platform level, at mcp.exepad.com, and drives your account: create an app, inspect it, edit it, publish it. A published app serves its own users and exposes no tool endpoint of its own. Anything you have read to the contrary is wrong.
How do I follow a build without hammering the API?+
Every build is an edit with its own record. Ask for its detail when you want a snapshot, stream it when you want live progress, read its logs when it finishes, and cancel it while it is still running. Builds take minutes, so wire up the stream first.
Can I undo a bad publish?+
Yes, on the API. Every publish lands in a history you can list, and a single call puts an earlier one back. Unpublish is there too, for when the right move is taking the app down entirely while you work out what went wrong.
Free covers simple web apps — three of them, one live at a time. The developer API is not part of it, and there is no free developer tier.
The developer API requires an active Pro subscription at $25/month and a funded wallet balance, or auto-reload enabled; usage is billed per operation from that balance. Pro also carries unlimited full-stack apps, 50,000 records, your own domain, and advanced AI models.
See plansOne key. One API. Whole apps.
Create it from a description, patch its files, publish it, and put the last version back — without leaving your terminal.
Get an API key →