The Facilitator bridges the HTTP payment layer and on-chain settlement. It stands between agents and the Scribe Finance contracts on Robinhood Chain, handling verification, transaction submission, and, once payment sessions ship, session management.

What the Facilitator does

For each payment or subscription an agent authorizes, the Facilitator:

1. Receives the agent’s signed authorization
2. Verifies the agent’s wallet balance covers the operation
3. Submits the transaction to Robinhood Chain and waits for confirmation
4. Returns a signed confirmation header to the service provider
5. The provider validates that header before serving the resource

The Facilitator also drives automatic subscription collection, calling the Scribe Finance Subscriptions contract at each billing cycle to collect from subscriber wallets.

During beta: a single operator

Throughout the beta, Scribe Finance operates the Facilitator as one centralized service. This is a trust dependency, and the protocol documentation states it plainly.

Running it centrally during beta means Scribe Finance can:

• Iterate on protocol mechanics quickly
• Maintain reliable uptime SLAs without the complexity of operating a decentralized network
• Detect abuse patterns and respond immediately

The tradeoffs are real and remain so: a single Facilitator is a single point of failure, and relying on it means trusting Scribe Finance as its operator. What it does not mean is trusting Scribe Finance with funds. The Facilitator holds no custody. It submits transactions on agents’ behalf, but every authorization rule is enforced by the Scribe Finance contracts on-chain: absent a valid on-chain authorization, the Facilitator can move nothing.

After beta: a permissionless network

Phase 3 of the roadmap (Q1 2027) opens the Facilitator to anyone. Operators run nodes by staking collateral on-chain, and that stake is the accountability mechanism: misbehavior or downtime costs the node its collateral.

Agents and service providers then choose which Facilitator(s) to trust: a specific set, or any node from the approved pool. The protocol itself is unchanged; only the operator layer opens up.

Failure modes

The Facilitator is unreachable

An unreachable Facilitator surfaces as an SDK-layer error on new payment requests. Active subscriptions are unaffected: their authorizations live on-chain and remain valid, and collections can run directly against the Scribe Finance Subscriptions contract until the Facilitator returns.

The Facilitator submits a bad transaction

The contracts enforce authorization rules on their own. The Facilitator has no say. It cannot approve a transfer beyond the on-chain authorized amount, cannot collect on a cancelled subscription, and cannot forge a payment proof that a service provider’s verification would accept. What is written to the chain governs; the Facilitator merely delivers.

Scribe Finance stops operating

Every subscription and allowance authorization is recorded on-chain, so the deployed Scribe Finance contracts outlive Scribe Finance the company. Providers can collect by calling the contracts directly, bypassing the Facilitator entirely. The chain is the source of truth.

Talking to the Facilitator directly

The SDK handles Facilitator communication, so most integrations never do. For custom integrations and alternative SDK implementations, the Facilitator API reference lives at https://facilitator.scribefinance.org/docs.