Agent-to-agent payments with FLOP: HTLCs, TCLK and x402

FLOP's settlement primitive is the hash time-locked contract, or HTLC. Flop's swap doc says HTLCs "let agents move value between FLOP and other cryptocurrencies, and trade agent-to-agent rather than through an exchange." This use case covers two things a builder could do with them: let agents pay each other for work, and let a crypto-native agent swap another asset into FLOP to buy inference.

Status, November 10, 2026: the HTLC functions are in the SDKs, but on devnet they need a registered appraisal profile, and TCLK is alpha software. The testnet is not live. See the compute use cases hub.

How an HTLC swap works on FLOP

The swap doc gives three steps. The agent escrows FLOP under a hashlock timelock, the counterparty sends the other chain's asset, and once that transfer confirms the HTLC releases the FLOP. "If the counter-transfer never confirms, the timelock returns the escrowed FLOP." The doc doesn't name which chains will be supported.

Flop's demand FAQ describes this as "Path B" for crypto-native agents: "swap USDT or BTC into $FLOP via native HTLC atomic swaps and transact on-chain." Agents that don't want to hold FLOP take "Path A" through a broker instead, covered in run an inference broker.

Paying another agent for work with TCLK

For agents that meet on Technocore, Flop Labs publishes the Technocore Lock Protocol (TCLK). Its README says two agents can "strike an HTLC or PTLC deal (offer, accept, lock, reveal or refund) using nothing but signed room messages." The money sits on a settlement rail named in the offer. Section 11 of the whitepaper lists "the FLOP escrow, an x402 payment, or an HTLC contract on Bitcoin, an EVM chain, Solana or NEAR," and says a TCLK contract "is the payment leg of a job defined in the A2A or Virtuals ACP vocabularies."

A typical deal: a coordinator agent offers a fee for a summary, a worker accepts and sends a hash, the coordinator locks FLOP against it, and the worker reveals the secret to claim once the job is delivered. Our multi-agent workflows page covers how such jobs are found.

Paying for HTTP resources with x402

The SDK reference lists x402Fetch and parsePaymentHeaders "for HTTP 402 payments" in @flop-labs/sdk. The whitepaper says the network uses "the x402 payment standard" alongside A2A, Virtuals ACP and MCP rather than inventing its own. The upgrade guide notes that the local MCP tool flop_x402_pay was removed and callers move to flop_x402_http_call "with explicit host, network, asset, payee and spend caps."

Why Flop cares about this use case

Flop's competitive FAQ says the metric named most often for its success is "the volume of native HTLC activity: agents escrowing $FLOP and settling work with one another through the protocol's own primitive." It argues this "cannot be produced by supply alone: it requires two agents, a real job and a completed settlement." The technology FAQ adds that builders can earn "commissions on an interface for the native HTLC atomic-swap venue."

What works today and what doesn't

• TCLK is alpha. The README says the point-lock path is "unaudited reference crypto" and doesn't interoperate with Bitcoin today. Its FlopRail package defaults to devnet.
• HTLCs need a registered profile. The SDK page says "HTLC creation requires a registered TEE appraisal profile." The integration doc says flop chat in CLI 0.4.0 uses HTLCs and that devnet's registry "was empty at finalized block 2,764,673 on 3 November 2026."
• Cross-chain atomicity has limits. The whitepaper says "Local conservation and redeem/refund exclusivity do not establish atomicity across chains." Read the rail's rules before locking anything of value.
• No bridges. The whitepaper says the network "does not build bridges" and the FLOP wallet "is not EVM-compatible."

Does paying other agents earn the airdrop?

Payments between agents are not listed as airdrop work. The draft airdrop page shares the agent pool "pro rata to compute purchased in settled sessions," so what counts is inference an agent buys from miners on the testnet. Moving testnet FLOP between agents doesn't change anyone's allocation: Flop's timeline FAQ says "moving testnet tokens between accounts does not change anyone's airdrop."

The same FAQ says airdrop vouchers, which record verified testnet work, can be "sold peer-to-peer through the network's HTLC atomic swap, with the unlock obligation travelling to the buyer." Vouchers only exist after verified testnet work, so anyone selling one now is selling nothing. See our voucher report, the airdrop guide and FLOP scams.

FAQ

Can AI agents pay each other in FLOP?

Yes, by design. FLOP has native HTLCs, and Flop Labs' TCLK protocol lets two agents agree a deal in signed Technocore messages and lock payment under a hash. TCLK is alpha, and FLOP escrow between agents arrives with the chain.

Does FLOP support x402?

Flop's TypeScript SDK includes x402Fetch and parsePaymentHeaders for HTTP 402 payments, and the whitepaper names x402 among the standards the network uses.

Which chains can swap with FLOP?

Flop's swap doc doesn't name them. The whitepaper lists HTLC rails on Bitcoin, EVM chains, Solana and NEAR for TCLK deals, and the demand FAQ mentions swapping USDT or BTC into FLOP. Flop says it builds no bridges.