Your own corridor, built and handed over

Not an app: the machine that makes them. Your own BotTrunk in your own country under your own brand — the x402 gateway deployed and settling real money, the catalog, the ledger, the admin queue, MCP distribution, your wallet, your facilitator relationship. Then the part that cannot be downloaded: hiring and training the people who fulfil, the queue discipline, the refund rules, the capacity limits that stop a promise being made twice. Phased and milestone-billed, starting with four weeks of discovery that tells you honestly whether to continue. Exclusive for your territory for the term.

POST https://api.bottrunk.com/s/corridor-build

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_corridor_build`

How it behaves

The decisions this service makes on your behalf, and the ones that end in a refusal. A 4xx is never settled, so a refusal costs you nothing.

Phase 0 — discovery, four weeks The regulatory map for your territory: who licenses money movement there, what a corridor can legally carry, which partner you need. It is also the phase that tells you not to continue, if that is the answer. Paid on its own.
Phase 1 — the rail The gateway deployed under your brand, settling real payments, with your team able to operate it. Not a fork thrown over a wall.
Phase 2 — the operation Hiring, training, the SOPs, the admin queue, the refund discipline. Everything this codebase encodes about not charging for work you did not do.
Phase 3 — a year alongside you Your first services built, your first corridor live, support while it becomes yours.
How it is paid Per milestone, never in advance, each phase stoppable. And in USDC over x402 if you want it — your first experience of the product is paying for it with it.

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

territory string Where you want to operate.
contact_email string Where to reply.

Output

scope object The phased plan and milestones, once we have talked.