The FLOP devnet suite / Build

Build

How do I integrate with FLOP correctly?

Start with the public interfaces and examples you can replay. Trace a result to its documented contract before integrating it.

9 available / 10 registered tools

Alpha is a release label. Every value below is a dated recording, not a current health claim.

10 tools shown

consolealpha

MCP console

What does each public tool return and how is its devnet cost estimated?

34

tools in recorded MCP discovery

Recorded / last known

Discovery only. Not every tool has an output schema or is enabled in the console.

Open tool ↗
yellowpaperalpha

Spec reader

What does the yellowpaper say beside the observed value?

182

parameters in the pinned yellowpaper

Recorded / last known

Pinned specification rows. Catalog agreement does not verify deployed runtime storage.

Open tool ↗
exportalpha

Data export

How do I get devnet data into a spreadsheet or notebook?

5

block rows in the export recording

Recorded / last known

Bounded recorded rows. Export completion does not establish chain completeness.

Open tool ↗
openapialpha

Suite API

How do I read the suite's results as an API?

25

settlement rows in the API tape sample

Recorded / last known

Bundled arithmetic summary. No inference or current network health is verified.

Open tool ↗

Reading guide

From a question to evidence

The line tracks your place in this explanation.

Choose a tool

Start with the question it answers. Planned tools link to their source location.

Read the date and source

A recorded value describes its capture. Public devnet data can change or disappear after a reset.

Inspect the boundary

Open the tool for its full evidence and reproduction command. A passing check covers only the stated claim.