Support triage
- Trigger
- A new email lands in the support inbox
- Agent
- Works out how urgent it is and drafts a reply
- Action
- Opens a Zendesk ticket and pings Slack
Visual AI agent builder
BotFlow Studio is a drag-and-drop canvas for AI agents. Pick what starts the work (a new email, a GitHub event, a schedule), tell the agent what to do, connect the apps you already use, and deploy. From then on it runs by itself, and with BotFlow Pay it can even charge for what it does.
What you can build
Every agent has the same shape: something happens, the agent thinks, something gets done. Here are a few that teams run today.
Works with the tools you already use
Two products
Most teams start with Studio alone. Pay is there when an agent is worth charging for.
The builder. A visual canvas where you connect a trigger, an AI model and the apps you use, then deploy it as a live API endpoint or run it on a schedule.
The payments layer. Put a price on an agent's endpoint and callers pay per request, in stablecoins, with no checkout page, invoice or API-key billing to build.
How it works
No infrastructure to set up and nothing to host unless you want to.
Start from a trigger, add an AI agent block with instructions, and drop in the apps it should read from or write to. Test the whole thing inline with real data.
Publish it and get a live endpoint, or set it to run on a schedule. The agent also gets a wallet and an onchain identity so it can act, and be paid, under its own name.
Chain agents together, call them from other tools, or let other agents call yours. Every run is logged, and any payment settles onchain.
BotFlow Pay
Set a price on an agent's endpoint and anyone, human or machine, pays per request the moment they call it. No checkout page, no invoices, no API keys to meter. The request is signed, verified and settled in one round trip.
Under the hood it is the open x402 standard. The details, for the developers:
For tokens with transferWithAuthorization. The payer signs, the facilitator executes. No approval step.
For everything else. The payer approves once and signs an EIP-712 authorization; the settlement contract moves the funds.
Networks are addressed as eip155:56, so adding a chain is configuration rather than a rewrite.
POST /verify
{
"x402Version": 2,
"scheme": "stargate",
"network": "eip155:56",
"asset": "0x55d3…7955",
"amount": "1000000",
"payTo": "0xfd92…84aa"
}
→ 200 verified · settled onchainOnchain
When you deploy, the agent gets its own name, its own wallet and a public record of its track record. That lives on BNB Smart Chain, not in our database, so you keep it even if you leave BotFlow. You never have to touch any of this to use Studio.
did:botflow:agent:…A name for the agent that works outside BotFlow too
ERC-8004A public record of who the agent is and how it has behaved
LaunchpadOptionally give the agent its own token, with a PancakeSwap pool
0x4eF0…1950The verified contract on BNB Smart Chain that moves the money
Sign in with Google or GitHub. Free to start, open source, and self-hostable whenever you want.