Community pulse →
What are operators and builders asking for and how long do public replies take?
flop communityBuild / Suite documentation
Find your question.
Run the check.
Package guides for the FLOP devnet. Find a command, read its evidence and keep its limits.
40 of 40 package READMEs match this search.
Observe
What is the network doing right now and over time?
Chain explorer →
What is in this block, transaction, account, compute channel or HTLC?
flop exploreFinality monitor →
Is the chain producing and finalizing blocks on time?
flop finalityModel registry →
Which models are served, at what price and are they registered?
flop modelsNetwork history →
How has the devnet changed between observations?
flop historySession lifecycle →
Where is a compute channel in its lifecycle?
flop sessionsService status →
Are FLOP's public services answering?
flop statusUpgrade tracker →
What changed in the runtime and in the spec?
flop upgradesVerify
Do the claims hold when checked from outside?
Emission and fees →
Do rewards, emission and inference fees follow the spec?
flop economicsConformance harness →
Does the network do what its docs say?
flop harnessIndexer audit →
Does the FLOP indexer agree with itself?
flop indexerSecurity invariants →
Which security invariants and failure cases can be checked from outside?
flop invariantsMCP contract audit →
Do FLOP's MCP tools return what they advertise?
flop contractsMetering and calibration →
How is effective FLOP counted and when does a miner's calibration expire?
flop meteringProof explorer →
What proofs are miners submitting and what do they cover?
flop proofsSpec differ →
Does the running devnet match its yellowpaper?
flop specSettlement verifier →
Do the settlement, receipt and attestation agree?
flop verifyBuild
How do I integrate with FLOP correctly?
CI checks →
Can a project run FLOP evidence checks in CI with a fixed request budget?
flop actionflop →
Which flop-lab tool answers my question?
flop --helpMCP console →
What does a public FLOP tool return right now and how is its devnet cost estimated?
flop callAgent starter →
How do I start a FLOP agent that is safe by default?
flop startData export →
How do I get devnet data into a spreadsheet or notebook?
flop exportShared recorded responses →
Which exact response did a test use and when was it observed?
Importable libraryKnowledge catalog →
What does the network's own knowledge catalog say and what does an agent pack contain?
flop knowledgeFLOP MCP client →
How do I read FLOP's public data without rebuilding the transport?
Importable librarySuite API →
How do I read the suite's results as an API?
flop apiRelease previews →
Can a contributor preview package versions and inspect exactly what a release would contain?
Importable librarySDK conformance →
Do the FLOP SDKs behave as documented?
flop sdkPay-per-call kit →
Does my paywalled API speak FLOP's 402 protocol correctly, from both sides?
flop x402Spec reader →
What does the yellowpaper say about this, next to the public value?
flop spec-readOperate
Is my miner or validator ready to join?
Operator doctor →
Is this machine ready to mine or validate on FLOP?
flop doctorStake and slashing →
What stake does my miner or validator need and what can it lose?
flop stakeWatcher →
How do I get told when the devnet changes?
flop watchAgents
How does an agent spend, route and dispute safely?
Challenge watcher →
Is a settlement worth review and is its challenge window still open?
flop challengeflop-lab MCP server →
How does an agent call flop-lab tools?
flop mcpMiner scoreboard →
Which miner has evidence I can rely on over time?
flop scoreSpend guard →
Will my policy hold when agents share one budget?
flop guardSwap planner →
Is this atomic swap safe to start?
flop swapDeal inspector →
Did this agent-to-agent deal follow the protocol?
flop tclkIdentity
Who did this work and can I check it?
DID trail →
What has this did:key signed and does it verify?
flop didReading guide
From question to evidence
The line tracks your place in this explanation.
Choose a section
Observe the network. Verify a claim. Build an integration. Operate a node. Set agent policy. Check who signed the work.
Run the package command
Start with the README quick start. Use flop to find the tool's own options. Recorded fixtures let you inspect evidence offline.
Keep the limits with the result
Read the source time and the final limits section. An unavailable check is not a pass. The devnet can reset.
Planned tools
These registry entries have no package README in this build.
- Python client ↗: How do I use flop-lab from Python?
Other integration
FLOP for Kestra has its own plugin guide on the tool page.