// protocol

Designed from
the ground up.

Proco is not a wrapper around existing rails. It is purpose-built financial infrastructure for AI agents — non-custodial at the protocol level, designed for machine-scale autonomous transactions.

Four layers.
One API call.

Every payment flows through four layers — each handling a distinct concern. Your code only touches layer 04. The rest is Proco.

04
Your application
SDK call · webhook handler · your code
03
Proco API
compliance + routing + cost abstraction
02
Smart router
Optimal path selected automatically
01
Instant settlement
Funds confirmed · immutable receipt · <30s

Three networks.
Auto-routed.

Proco selects the optimal settlement network for every transaction based on speed, cost, and destination. No configuration needed — override when required.

You don't need to know which network to use. Proco auto-routes every payment to the optimal network based on speed, cost, and destination. Override when you need to. Ignore when you don't.

Base
8.2s
avg settlement
Fastest for most payments. Low cost, fast confirmation. Default for agent and enterprise payments.
P0 · default
Solana
0.4s
avg settlement
Sub-second settlement. Best for micropayments and high-frequency agent-to-agent transactions where speed is critical.
P0 · low latency
Ethereum
12.1s
avg settlement
Highest value and broadest compatibility. Used for large enterprise settlements and protocol-level integration.
P1 · enterprise

Non-custodial by design.
Not by policy.

Most payment infrastructure holds funds in transit — creating counterparty risk and custody requirements. Proco's protocol is non-custodial at the core: funds move directly from sender to recipient on-chain. No escrow, no intermediary balance sheet, no counterparty exposure.

What this means for you: Proco never holds your money. You never hold Proco's risk. Funds move directly from sender to recipient. Think of it as a payment rail with no middleman balance sheet.

No MTL required

Because Proco never holds customer funds, the Money Transmitter Licence burden doesn't apply to the majority of use cases. Deploy globally from day one.

No counterparty exposure

Your USDC moves directly between on-chain addresses. At no point does Proco hold a balance on your behalf. Funds are never at risk from Proco's operational status.

Immutable on-chain receipt

Every settled payment creates an immutable on-chain record. The txHash, amount, timestamp, and compliance reference are verifiable by any party, at any time.

Rules travel with the funds

Compliance logic, spend policies, and conditions are encoded at the protocol level. They execute atomically with settlement — no async middleware, no race conditions.

Compliance travels
with the payment.

Set compliance: 'auto' and Proco handles the full compliance stack automatically. The rules are evaluated at the moment of trigger — before funds ever move.

You write three lines of code. Proco handles KYC, KYB, KYA, AML, sanctions screening, and the FATF Travel Rule automatically — before funds ever move.

KYA — Know Your Agent.

Traditional compliance was built for humans. KYC verifies a person. KYB verifies a business. Neither was designed for a non-human principal operating autonomously at machine speed. Proco introduces KYA — Know Your Agent. Every agent wallet carries a verified identity: who owns it, what it's authorised to do, and what its spending limits are. When an agent initiates a payment, Proco verifies the agent's identity and authority before funds move.

// agent identity record
agent_id: agent:worker-0x4f
principal: org:acme-corp
authorised_spend: $500/day
policy: task.completed required
compliance: auto · KYA verified ✓
KYA
agent identity
KYC / KYB
identity verification
AML
transaction screening
Sanctions
OFAC · EU · UN
Travel Rule
FATF compliant
Settlement
on-chain · atomic

Every condition met
is a payment fired.

From trigger to on-chain confirmation, p99 under 30 seconds. The flow is deterministic — the same four steps every time, with a full audit trail at each stage.

01
Trigger fires
event · schedule · agent · condition · API call
02
Compliance evaluated
KYC · KYB · AML · sanctions · Travel Rule · <2s
03
Network selected
auto-routed · cost abstracted · optimal p99
04
Instant settlement
Funds confirmed · txHash · immutable receipt · webhook

Infrastructure you
can audit.

Every component of Proco's protocol is designed with auditability in mind — from on-chain transaction records to HMAC-signed webhook delivery.

Non-custodial architecture

Proco never holds customer funds. Verified by design — no escrow smart contracts, no custodial wallets.

OFAC + UN + EU sanctions

All parties in every transaction are screened against live consolidated sanctions lists before funds move.

FATF Travel Rule

Originator and beneficiary information is collected and transmitted for qualifying transactions, automatically.

On-chain audit trail

Every settlement creates an immutable on-chain record. Any party can verify txHash, amount, and timestamp independently.

ISO 27001 (in progress)

Formal information security management certification currently in scope. Expected Q3 2026.

What developers are
building with Proco.

Real infrastructure for real use cases. These are the systems developers are shipping today.

AI hedge funds

Autonomous trading agents that pay for data, execute settlements, and sweep treasury positions 24/7. No human in the loop.

Multi-agent research systems

Orchestrators that spin up specialist sub-agents and pay them per task completion. $0.004 per search. $0.018 per analysis run.

Autonomous AP pipelines

Invoice arrives, conditions verified, payment fires. No approval queue. No human sign-off. Accounts payable without the payables team.

DeFi protocol treasuries

On-chain agents that rebalance liquidity, route yield, and execute grant disbursements the moment governance resolves.

x402 API servers

Charge other agents per API call automatically. One line of code. Proco handles the payment when the 402 fires and grants access immediately.

Read the protocol docs.

Deep technical reference, API spec, and integration guides — all in the developer docs.