What is Clicks Protocol?

Clicks Protocol is an agent commerce settlement router on Base. It keeps agent working capital liquid and routes the idle slice into Aave V3 or Morpho using a programmable split. Non-custodial, withdraw anytime, ERC-8004 agentId 45074.

How do I integrate Clicks Protocol?

Install the SDK with npm install @clicks-protocol/sdk, then call clicks.quickStart(amount, agentAddress). For MCP-compatible agents, use npx @clicks-protocol/mcp-server with 16 built-in tools, including receipt verification, read-only reconciliation, referral attribution and protocol explanation.

2% fee on yield earned only. Never on principal. No deposit fees, no withdrawal fees. If your agent earns $100 in yield, the fee is $2.

Is Clicks Protocol safe?

6 contracts verified on Basescan (Registry, SplitterV4, FeeV2, YieldRouter, Referral, plus Safe multisig owner). 227/227 tests passing. Non-custodial (your keys, your funds). Immutable contracts (no proxy, no admin keys). ReentrancyGuard on all functions. MIT licensed and open source. V2 upgrade (April 2026) wired referral distribution and transferred ownership to Safe multisig 0xaD8228fE...

Can I withdraw anytime?

Yes. No lockup periods, no vesting, no cooldown timers. Withdraw your full principal plus earned yield at any time.

Clicks Protocol

Case study · Base Mainnet · July 2026

x402 payment followed by Clicks settlement on Base

x402 verified and settled a 0.01 USDC payment. Clicks then applied the seller's settlement policy and produced public routing evidence on Base.

What we tested

1An isolated buyer wallet authorized an x402 payment.
2Coinbase Developer Platform verified and settled it through EIP-3009.
3The seller approved ClicksSplitterV4 for exactly 0.01 USDC.
4Clicks routed 0.008 USDC to the liquid destination and 0.002 USDC to ClicksYieldRouter.

Public evidence

Three successful transactions

No retry

x402 payment

The USDC Transfer event records payment from the isolated buyer wallet to the seller.

0.010 USDC

Block 48965057

Exact allowance

The seller approved ClicksSplitterV4 for the test amount only. The remaining allowance after routing was zero.

0.010 USDC

Block 48965425

Clicks settlement

The PaymentReceived event records 0.008 USDC liquid and 0.002 USDC routed to ClicksYieldRouter.

80 / 20

Block 48965428

Total

0.010 USDC

Liquid

0.008 USDC

Routed

0.002 USDC

Live integration check

We also ran a moneyless test against the private integration. It checked receipt creation, append-only persistence, deduplication and idempotency conflict handling without signing a payment or submitting another Base transaction.

Repeating the same verified revenue event returned the existing receipt. Reusing its payment key with a different amount was rejected.

ACP Mainnet evidence

A funded agent job completed end to end

A bounded ACP job moved 0.01 USDC through funding, agent registration, an exact splitter allowance and Clicks routing on Base Mainnet. The job completed with 0.008 USDC routed to the agent and 0.002 USDC to ClicksYieldRouter.

All five transactions succeeded. The remaining splitter allowance was zero. The receipt trail reached planned, submitted, chain confirmed and settled without a second funding transfer.

Buyer fundingBlock 48971486 ACP fund transferBlock 48971517 Agent registrationBlock 48971733 Exact allowanceBlock 48971735 Clicks routingBlock 48971738

Current limitation

The x402 payment and Clicks settlement were separate Base transactions. They were not atomic: the payment could succeed even if the later routing transaction failed or was delayed.

Reconciliation therefore keeps both transaction references as separate evidence. This test proves the post-payment routing path, not a single all-or-nothing transaction.

Pilot with Clicks

Testing an agent commerce payment flow?

We are working with a small number of teams that need revenue routing and verifiable settlement receipts after payment.

Discuss a pilot