One agent. Many clients. Each funds their own intelligence.
Problem Agitation
“An AI automation agency can run one shared workflow for many clients. But every inference request raises the same question: Whose balance pays for it? When everyone spends through one account, billing gets blended, margins become unpredictable, and one client's usage can become another client's problem. Separate provider projects add setup and maintenance. Client-owned accounts add keys, payment cards, and onboarding friction. Front the cost yourself, and you are left estimating usage after the fact. The infrastructure can be shared. The economic identity should not.”
Product Reveal
“FlowFuel lets an agency operate one shared lead intelligence agent while each client funds their own intelligence through Orbio. The agency owns the workflow. The client owns the budget. FlowFuel keeps the payer attached to the run.”
Feature Teaser
“A lead arrives through n8n. FlowFuel resolves the client identity, selects that client's encrypted Orbio credential, and sends the run to the gateway. The agent can plan, choose the website inspection tool, observe the site, reason over what it finds, and return structured qualification. The workflow stays shared. The credential and balance do not.”
Feature Teaser
“Now watch the same workflow run against different clients. Client A is funded, so two generations complete and the client pays for the run. Client B is unfunded. Orbio returns HTTP 401. FlowFuel records zero generations and no charge, and n8n takes the funding required branch. Client C enters through USDG, Orbio exchange, and buy and activate, receives credit, and uses the same agent. The payer changes per run. Client D shows what happens when the balance can manage itself. The live trigger snapshot is 1.270882, below a $2 trigger. FlowFuel detects the threshold and applies a fixed policy: refill 1 USDG, cap weekly spend at 3 USDG, allow 2% slippage, and send the activated balance only to Client D.”
Feature Teaser
“The vault spends 1 USDG, receives 1.225490 credit, and records activation 274. This is a real transaction.”
Feature Teaser
“The refuel is indexed. A subsequent continuation uses the funded balance, runs two generations, and succeeds.”
Feature Teaser
“The original trigger run is shown honestly as provider failed after the refuel, not rewritten as a completed task. Orbio is the programmable inference economy underneath FlowFuel. Wallet-derived credentials, credit, USDG, the exchange, live balance reads, and generation accounting make client-owned agent spending possible. n8n orchestrates the workflow. FlowFuel enforces client isolation and runtime policy. Orbio supplies the funding and inference primitives.”
Feature Teaser
“Under the hood, credentials are encrypted, identities are wallet bound, runs are idempotent, costs are reconciled across generations, and no fallback account exists. Refuel policy and weekly limits are enforced on-chain. Today the reference workload is lead intelligence. Next comes support, research, document, sales, and vertical agents.”
Call to Action
“The agency operates the agent. The client sets the budget. FlowFuel keeps it running. One agent, many clients. Each funds their own intelligence.”
Synthesizable in Remotion · key components of the technical-slide-deck template.
Dark slate background (#0c0e0c) overlayed with fine architectural grid, page index '01 / 09' in bottom right, and category metadata in corners.
Absolute container with SVG 40px grid pattern, mono header trackers using AbsoluteFill, and subtle border lines.
Rectangular node with subtle border, status dot, and connector lines linking client entities to shared agent hub.
Flex container with border, dynamic status tag, and SVG paths rendering connecting lines using strokeDashoffset.
High-density data readout mimicking transaction receipts and API logs with highlighted JSON keys and red/green HTTP codes.
Monospace table layout wrapped in a simulated browser frame with color-coded status badges and SVG highlight rects.
Purpose. Explain the architectural paradox of multi-tenant AI agents sharing a single billing key.
Execution. Architecture diagram contrasting 4 client states connected to a central Lead Intelligence Agent node.
Purpose. Show the runtime abstraction layer ensuring each request binds to isolated client wallets.
Execution. Split view detailing step-by-step routing protocol and n8n broker configuration.
Purpose. Demonstrate live isolation across funded, unfunded, self-serve, and autonomous refuel paths.
Execution. Real dashboard telemetry showing HTTP 200, HTTP 401 boundary stops, and automated on-chain refuels.
Purpose. Solidify the agency value proposition: shared workflows with client-funded autonomous compute.
Execution. Bold tri-color typography lockup with URL and architectural role definition.