Currently in testnet

Payment rails for
autonomous agents.

Polyflow is non-custodial payment infrastructure for AI agents — owner-defined spending policies enforced cryptographically, across Litecoin and Arc, from one API. Running on testnet today, with early access opening in phases.

Request early access View architecture
testnet only · mainnet access opens in phases
quickstart.py
from polyflow import Agent agent = Agent.create(owner_api_key="pf_test_...", name="research-agent", rail="ltc") agent.set_policy(daily_limit="0.5 LTC", per_tx_limit="0.5 LTC", approval_threshold="0.5 LTC") agent.fund_address() # backend co-signs automatically once the policy check passes tx = agent.pay(to="data-agent-042", amount="0.05 LTC", purpose="dataset access") tx.wait_confirmed()
Currently in testnet
Full API opens with mainnet — request early access
Why it's different

Enforcement lives on-chain, not in a database.

Every payout requires the backend's cryptographic signature — not just a policy flag. If Polyflow's servers disappear, your agent's funds don't.

Non-custodial

Two-key control on every rail. Polyflow never holds a key capable of moving funds alone.

Policy enforcement

Daily limits, per-transaction caps, and approval thresholds — checked before any signature is issued.

Dual-rail

One integration, two settlement networks. Litecoin for battle-tested UTXO transfers, Arc for sub-second finality.

Built for agents

Webhooks, approval flows, and reputation-ready primitives designed for machine-speed decision loops.

Settlement rails

Two networks, one interface.

The SDK hides which rail an agent runs on. Pick per agent, switch later, same API shape.

Litecoin
Litecoin
UTXO · 2-of-2 multisig
Testnet

Agent wallets are 2-of-2 P2WSH multisig — one key on the client, one on the backend. Nothing moves without both.

P2WSH multisig ZMQ confirmations testnet4
Arc
Arc
EVM · vault contract
Testnet

A minimal per-agent vault contract requires both the agent's and the backend's signature for every payout — sub-second deterministic finality.

AgentVault.sol USDC-native gas testnet
How a payment flows

From request to settlement.

1

Agent requests a payment

The agent signs its half of the transaction client-side and calls the API with the intended amount and recipient.

2

Policy check runs

Daily limit, per-tx cap, and allow/deny lists are checked against the agent's owner-defined policy.

3

Co-sign or hold

Within policy, the backend co-signs and broadcasts. Over threshold, it holds for owner approval via webhook.

Get early access

Be first when mainnet opens.

Polyflow is live on testnet today. Request early access and we'll reach out as mainnet rails open, starting with Litecoin.

Request early access