Skip to main content
FlowFabric
Built on FlowVault + Stacks

Let agents pay.Never let them overspend.

FlowFabric gives an AI agent a scoped on-chain allowance. Every payment is checked against a policy - cap, expiry, allowed recipients - before it settles. The owner key never leaves the wallet.

  • FlowVault
  • Stacks
  • MCP
  • STX
  • Hiro
  • x402
  • Clarity
  • Testnet

AnAIagentcanhitapaidAPI,splitapayroll,orsettleaworkflowonitsown-butonlyinsidelimitsyouset.FlowFabricturnsFlowVaultLockandSplitprimitivesintoadelegationlayer,soagentsgetautonomyandyoukeepcustody.

The primitives

Three FlowVault primitives, one delegation layer

Lock

Funds are time-boxed by block height. The agent cannot spend past the expiry you set.

Split

One agent decision routes payment to the right recipient - or splits across a team - on-chain.

Hold

The vault holds funds and releases only what the policy allows. Owner key never leaves the wallet.

How it works

Autonomy without custody

01

Fund + scope

Owner funds a vault and sets a policy: max spend, expiry block, allowed recipients.

02

Delegate

A scoped session key goes to the agent. Capped, expiring, recipient-locked - not the owner key.

03

Agent pays

The agent calls agent_pay over MCP. The policy engine checks every request before settlement.

04

Reject out-of-bounds

Over-cap, expired, or unknown recipient? Rejected before it touches the chain.

No custody

Leak the scoped key and the blast radius is a cap, an expiry, and an allowlist. The owner key is untouched.

Agent-native

Exposed over MCP: get_vault_state, list_policy, agent_pay, run_workflow. Any MCP client can drive it.

Composable

Chain a paid API call and an on-chain settlement in one bounded run. Rejected steps never spend.

Give your agent an allowance, not your keys.

Open the dashboard