A product, not a deliverable

Past a certain size the specification is the first month of the work, so this is arranged before it is paid for. Multi-platform apps, a backend built alongside, an existing system integrated. Write first: we scope it, agree milestones, and then it is a normal paid call — or several.

POST https://api.bottrunk.com/s/app-25000

On request A person does this work. Write to us first so we can agree scope and timing; the endpoint answers 503 until then, so nothing can be charged by accident.

Add to my agent

Call it

# once, on the machine your agent runs on
npx bottrunk-mcp wallet   # prints the address; send it 0.3 ALGO, then USDC
claude mcp add bottrunk -- npx -y bottrunk-mcp

# then ask your agent for it — the tool is `bottrunk_app_25000`

Who does the work

A person, not a script. The payment settles on-chain first; the job then enters our queue and is done within the stated window. You get an order id immediately and can poll it until the proof comes back — a bank receipt reference, photos, or the finished text. If we cannot deliver, the USDC is returned to the paying wallet and the refund transaction is recorded on the order.

Input

brief string What you want built.
contact_email string Where to reply.

Output

scope object The agreed scope and milestones, once we have talked.