Facilitator

Payment escrow built into the stack, the default rail for operators on Fabric.

Facilitator is payment infrastructure for streaming and usage-based jobs. It runs underneath Fabric, SimArena, and optr as the default payment rail, and it can also work independently for any service that needs metered escrow.

Why it exists

Open-ended robotics jobs do not behave like one-shot API calls. A Fabric GPU session, SimArena simulation, or optr streaming job may not have a known final cost before it starts.

• x402 is good for fixed requests: one-shot calls can be priced and settled cleanly.
• Streaming jobs need a hold: providers need funds reserved before they spend compute, while clients need unused funds returned when the session ends.

Facilitator adds that holding mechanism. A session can start with a maximum amount, draw down as usage is reported, and refund the remainder.

The default rail

When optr workflows deploy to Fabric through graph.deploy(), Facilitator can be the default payment handler. Operators can configure their own payment handler, but CodecFlow gives them a metered path out of the box.

• Operators paying for Fabric compute: sessions are funded through Facilitator escrow. Funds lock upfront, draw down per second, and unused funds return when the session ends.
• Operators getting paid for services: clients pay through Facilitator. The operator settles as work is delivered, without either side needing to trust the other directly.

How it works

Facilitator extends x402 with a holding step:

1. Client authorizes     -> signs payment for a maximum amount
2. Facilitator verifies  -> checks signature and available funds
3. Facilitator holds     -> moves funds into escrow
4. Provider delivers     -> streams compute, simulation, or data
5. Facilitator settles   -> releases funds as usage is reported
6. Session ends          -> unused held funds return to the client

The provider gets paid as work happens. The client pays only for what was used. The contract enforces settlement and refunds.

Note

x402 contribution

Facilitator comes from CodecFlow work on the x402 specification. The team proposed and built the first implementation of scheme_upto on Solana to fix the race condition where a client could drain a wallet between authorization and settlement.

The lock-then-serve model locks maxAmount into a program account at verify time, releases actualAmount to the recipient at settle time, and refunds the remainder. The client keeps the same sign-message UX, but funds are reserved before the provider serves resources.

References: x402 issue #1642 and PoC repo.

Where it is active

• Fabric: agents and operators pay per second from held funds, without setting up a traditional billing account for each session.
• SimArena: machine-driven usage can route through Facilitator, while product credits can still cover human users.
• optr: operator-to-consumer transactions can settle through the same rail.

Implementation

• Smart contracts on EVM chains and Solana
• Rust backend service for verify, hold, settle, and refund
• TypeScript SDKs for client and server integrations
• Dashboard for active sessions and settlements

Facilitator can also ship as an independent service for streaming APIs, compute platforms, real-time data feeds, and pay-per-minute software.