FLOP for AI agents: how agents buy inference on Flop

Flop Network has three roles: miners sell GPU inference, validators run the chain, and agents buy the inference. Flop's agent page puts it simply: an agent "posts a session request and pays miners in FLOP to run inference." This guide explains how that works for an AI agent, using Flop's draft agent page and its operator docs. It also covers what an agent needs when the testnet opens, with a working target of November 3, 2026.

All of this is draft design. Flop's docs mark the agent pages "Draft whitepaper," and the token doesn't exist yet.

What does an AI agent do on FLOP?

It pays for compute. Flop's agent page says the account-based chain lets an agent "convert currency into compute at any time, with spend limits enforced on-chain." An agent doesn't run a node or hold a GPU. It needs an identity, some FLOP and a way to send requests. Miners do the work and validators record the proof. Our what is FLOP guide covers the network as a whole.

How does an agent buy inference?

The session docs describe four steps: request, match, prove, settle.

1. Request. The agent posts a session request to the mempool.
2. Match. A miner with capable hardware accepts and opens a private connection with the agent. The payment sits in escrow.
3. Prove. The miner runs the inference and returns a proof: activation commitments and a co-signed transcript, plus a hardware quote if it runs the optional HARD tier.
4. Settle. Validators include the proof hash in a block. The miner gets the session payment plus a share of the block reward.

If the work is wrong, the doc says the agent "pays nothing and challenges instead." It adds that the end-to-end settlement and dispute path for the default SOFT tier "is still being specified." Our proof of useful inference guide explains how the proof is checked.

What goes in a FLOP session request?

Five fields, per the agent integration doc:

Field	What it fixes
Model-weight hash	Which model must run
Max latency	The deadline
FLOPs	How much compute the task is worth
Confidentiality flag	Whether the session needs the confidential path
Fee	What the agent pays, in FLOP

How does an agent stop itself overspending?

FLOP is an account-based chain, and the spend control doc lists the limits an agent account can carry:

• Pre-set spend limits, so the agent can't exceed the budget it was given.
• Proxies that hand another party a bounded capability instead of the whole account.
• Multisig, timelocks or vesting, and multi-party escrow pools.

The doc's reasoning is that an agent buying compute all day "needs the spending boundary enforced by the chain rather than by its own good behaviour," so a bug in the agent can't spend past it.

What if a miner does the work wrong?

The agent challenges it. The integration doc says a challenger posts a 100 FLOP bond, which it loses if the dispute is frivolous. If the network upholds a fraud verdict, the agent's escrow is refunded and the miner's stake is slashed in full. The staking and slashing rules and the challenge game are covered in our tokenomics and validator guides.

Can an agent pay with other crypto?

Not directly, but it can swap. FLOP has native hashlock timelocks (HTLCs), and the swap doc says an agent can escrow FLOP against another chain's asset and release it once the counter-transfer confirms. If the other side never pays, the timelock returns the FLOP. The doc doesn't name which chains will be supported.

Flop Labs' open-source TCLK protocol builds on the same idea for agents that meet on Technocore: two agents agree a deal in signed chat messages and lock the payment under a hash. Its README marks it as alpha. More on the code is in our FLOP GitHub guide.

What does an agent need for the FLOP testnet?

Very little. The timeline FAQ says an agent's day-one requirement is:

• An identity key, "the same DID key used on TechnoCore."
• The ability to make HTTP requests.
• The ability to call the testnet faucet and submit an inference request signed with that key.

It says "no wallet software, chain client or SDK beyond that is needed to start," with connectors for common agent frameworks to follow. The FAQ's steps are: create an agent with a DID key, claim testnet FLOP from the faucet when testnet launches, then have the agent spend it on an inference request. "The task itself does not matter."

Testnet FLOP has no value. Agents draw it from a faucet with per-identity limits, so the faucet caps how much inference each agent can buy on testnet. The how to join the FLOP testnet checklist has the full steps for every role.

Can an agent use FLOP today?

Only in a limited way. The devnet is running, and the timeline FAQ says "agents can already reach the devnet endpoints, rate-limited." The same FAQ also says routing real agent inference to FLOP is "not possible on devnet," which is closed to a small group of institutional partners. Devnet earns nothing.

Flop's direct session guide, updated October 20, shows how developers send a request to a named miner on devnet with a CLI, an SDK or a local MCP server. The --max-flop setting is the escrow ceiling, and transaction fees come on top. The guide notes that Flop's hosted MCP never exposes the tool that runs a paid session. The official links page lists that hosted MCP at mcp.flop.network as read-only. Our FLOP devnet guide covers the faucet and RPC.

Do agents get the FLOP airdrop?

Yes, from a dedicated pool. The draft airdrop page gives agents 1,200,000,000 FLOP, shared pro rata to compute purchased in settled testnet sessions. A faucet grant on its own doesn't count.

The agent airdrop arrives locked and can be spent only on compute. Flop's sources differ on how it unlocks:

• The airdrop page (updated October 5) and the timeline FAQ (updated October 20) say every 3 FLOP spent in settled sessions unlocks 1 FLOP, with no end date.
• The airdrop and testnet conversion doc (updated September 30) and the agent page say the release schedule "is not yet set."

Treat the 3:1 rule as the latest stated design, still subject to change. Our FLOP airdrop guide and the airdrop checker cover the agent steps in more detail.

Can an agent earn on idle FLOP?

The docs say yes, through the community staking pool. The integration doc says an agent can lock idle FLOP in the duration-locked pool to share the 5% staker slice of the block reward, and that "operator pools do not support delegated staking." Flop's agent page, updated later, mentions delegating stake to miners or validators. The two don't match yet.

There's also a separate 10% of each block reward for "agents and brokers." The tokenomics summary says it is minted to a protocol account and "not claimable today," with the payout rules still being designed. See FLOP tokenomics for the full split.

FAQ

How do AI agents use FLOP?

Agents use FLOP to buy AI inference. An agent posts a session request with five fields, a miner runs the job and returns a proof, and the agent pays in FLOP when the session settles. If the work is wrong, the agent can challenge it instead of paying.

What does an agent need to join the FLOP testnet?

A DID key (the same kind used on Technocore), the ability to make HTTP requests, and the ability to call the testnet faucet and sign an inference request. Flop's timeline FAQ says no wallet software, chain client or SDK is needed to start.

Does my agent earn the FLOP airdrop?

Agents share a draft 1.2bn FLOP pool pro rata to compute purchased in settled testnet sessions. Faucet grants alone don't count. The agent allocation is locked and can only be spent on compute.

How do agents control spending on FLOP?

FLOP accounts support pre-set spend limits, proxies with bounded authority, multisig, timelocks and escrow pools. The limits are enforced by the chain, so a bug in the agent can't spend past them.

What happens if a FLOP miner cheats an agent?

The agent can dispute the session with a 100 FLOP bond, which it loses if the dispute is frivolous. If fraud is upheld, the agent's escrow is refunded and the miner's stake is slashed in full.

Is Technocore part of FLOP?

Technocore is Flop Labs' chat and notes service for agents, and agents on testnet use the same DID key there. Its source says it settles nothing and holds no keys. Payment happens on the FLOP chain or another settlement rail.