Buildalphaopenapi

Suite API

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

Source and guide ↗
flop api --help

The same dated evidence. One JSON contract.

Read recorded suite results from your script. Every response keeps its source dates, limits and schema version. Reads do not start a live scan.

OpenAPI 3.1 document ↗GET + HEADNo key

Choose a result

Bundled evidence, preserved dates.

/api/v1/verifier

Verifier tape summary

Open tool ↗

Observed through . Mode: recorded.

curl --fail-with-body 'http://localhost:3780/api/v1/verifier'
25channels
50checks
PASS50
FAIL0
UNVERIFIABLE0
NOT_APPLICABLE0

What the result means

  • Only the first recorded settlement page is summarized. This is a bounded tape sample.
  • Escrow and displayed-price arithmetic do not verify inference, agreed pricing or movement of funds.

Example response

{
  "schemaVersion": "1.0.0",
  "tool": "verifier",
  "mode": "recorded",
  "measuredAt": "2026-11-05T08:59:55.135Z",
  "sources": [
    {
      "url": "https://mcp.flop.network/mcp",
      "measuredAt": "2026-11-05T08:59:55.135Z"
    }
  ],
  "recordings": [
    "https://github.com/zkasuran/flop-lab/blob/e1d4788/packages/verifier/fixtures/settlements-0.json"
  ],
  "revalidateSeconds": 300,
  "summary": {
    "metrics": {
      "channels": 25,
      "checks": 50
    },
    "outcomes": {
      "PASS": 50,
      "FAIL": 0,
      "UNVERIFIABLE": 0,
      "NOT_APPLICABLE": 0
    }
  },
  "limitations": [
    "Only the first recorded settlement page is summarized. This is a bounded tape sample.",
    "Escrow and displayed-price arithmetic do not verify inference, agreed pricing or movement of funds."
  ]
}
Sources and raw recordings (1)

Read the evidence contract

01 / SOURCE

Keep the date attached

measuredAt is the latest observation in sources. Each source retains its own time. It is never the time you called this API.

02 / VALIDATE

One schema, both ways

Response validation and the OpenAPI document use the same JSON Schemas. Missing evidence has summary: null. Invalid evidence returns HTTP 503.

03 / REUSE

Cache the data gently

Validated bodies revalidate after 300 seconds. The API allows 60 reads per IP per 60 seconds on each server instance. On HTTP 429, wait for Retry-After. HTTP 5xx merits backoff rather than a tight retry loop.

Only GET and HEAD are supported. Query parameters return HTTP 400. Unknown endpoints return HTTP 404. Other methods return HTTP 405. This API does not verify current uptime, inference or consensus.