builds

some things are easier to hand someone than to describe: a page for the event, a form that collects the answers, a small tool for the thing you keep doing by hand. your agent builds those. you describe it, it tells you what it will cost, it builds, and it comes back with an address you can send to anyone. this page is how that goes, what it costs, where the result lives, and what is switched on today.

how do i ask?

in chat, the way you would ask a person who can code:

make me a one-page site for saturday's dinner with the address, the time and a button to say you're coming

build a page where clients can book a 20 minute slot with me

it asks what it needs to know, then quotes the job before it starts.

what does it cost?

a quote first, then the real number. every build is quoted as a range with a ceiling before any work begins, and the quote comes from measured builds rather than a guess: a single page is a few cents, a fresh small site is tens of cents, and a multi-turn project is around a dollar. the ceiling is reserved from your daily allowance while it builds and the real cost is settled when it finishes, so you are never charged the ceiling for a job that came in under it.

a failed build costs you nothing. if the build fails, times out, or comes back without something to deploy, you are charged nothing at all, whatever it cost us. that is how the ledger is written, not a courtesy.

it draws on the same allowance as everything else. there is no separate build budget: if your daily allowance is used up, a build waits like the rest, and your agent tells you which of three things is true: the day's allowance is spent (it resets at midnight in your time zone), the build is bigger than your plan's whole day (a larger plan or a build pack fits it), or we broke something (nothing charged, our fault).

where does it live?

at a live address, or it is not done. a build is finished when it has an address; the platform will not call a build live without one. your agent sends you the address in chat the moment it is up.

on the builds page. instaclaw.io/builds keeps every build as a card: live or not, its address, what it cost, and a link that opens the conversation with your agent about that build. the page never edits a build itself; your agent is the one that acts.

can it have my own domain?

yes, and it stays yours. a build can be put on a domain of your own. if you ever want to take that domain elsewhere you do not have to ask us: pointing its nameservers away is immediate, and a full registrar transfer is a self-serve request with a 48-hour cooling-off period during which you are notified on every channel and can cancel, the same shape as recovering a wallet, because a domain exit is exactly what a thief would request first. registrars will not complete a transfer inside the first 60 days of a registration; the request is still yours to make earlier.

can it build without asking?

only if you switch that on. auto-build is a setting you control; your agent cannot turn it on for itself, and turning it off takes effect immediately. with it off, every build starts with you asking and approving the quote.

what is switched on today?

the machinery above is built and tested, and the rail is being switched on for customers in stages. today the intake is closed: no customer build has yet gone through it, and the builds page shows nothing until yours does. when the rail opens for you, this page will say so, and nothing here describes a build as available before it is.

what this page does not promise

a business in a box: a build is a small web thing, not a payment system, a customer database or an app-store submission. it does not promise the quote's ceiling will never be reached; it promises you never pay above it. and it does not keep building after you say stop.

what next

• your agent's computer: where the building happens
• plans and billing: the allowance a build draws on
• files: the pieces it makes along the way