FLOPS · Onboarding

Overview For finance teams For engineering teams

Use FLOPS in 10 Minutes

Settlement-grade GPU compute price indices, delivered through whichever surface fits how you work — a spreadsheet cell, an agent on Claude or Cursor, or a one-line cURL. Every published value carries a cryptographic receipt your code can verify.

1 Excel / Google Sheets — formula in a cell 2 min

The fastest path for finance teams already in a spreadsheet. The add-in registers 6 functions including =FLOPS.PRICE(), =FLOPS.TS(), and =FLOPS.METHODOLOGY().

Install

# Excel for Mac / Windows
Insert → Get Add-ins → Manage → Upload My Add-in →
  https://app.flopsindex.com/excel-addin/manifest.xml

# Google Sheets
Extensions → Add-ons → Manage Add-ons →
  https://app.flopsindex.com/sheets-addin/manifest.json

Use

=FLOPS.PRICE("FLOPS-H100-OD")
→ 6.155

=FLOPS.PRICE("FLOPS-H100-OD", "2026-05-15")
→ 6.213

=FLOPS.METHODOLOGY("FLOPS-H100-OD")
→ "flops-h100-od@v0.9 · k-anon ≥ 3 · MAD trim"

=FLOPS.RECOMPUTE("FLOPS-H100-OD", "2026-05-15")
→ "https://app.flopsindex.com/v1/audit/recompute/{run_id}"
The killer cell: =FLOPS.RECOMPUTE() returns a verifier URL. Drop it next to a settlement value in any model and the IOSCO audit trail follows the row.
2 MCP — Claude Code · Cursor · Windsurf · ChatGPT desktop 3 min

The agent path. flopsindex-mcp is on PyPI and exposes 9 tools over MCP — your agent answers "what's the H100 price?" or "verify this receipt" without leaving the chat.

Install

pip install flopsindex-mcp

Wire to Claude Code (or any MCP host)

// ~/.config/claude-code/mcp.json  (or Cursor settings)
{
  "mcpServers": {
    "flopsindex": {
      "command": "flopsindex-mcp",
      "env": {
        "FLOPS_API_KEY": "your-key-from-/admin-or-contact"
      }
    }
  }
}

Hosted gateway alternative

Don't want to manage a local process? Point the host at https://app.flopsindex.com/mcp — it speaks the MCP transport directly, no install required.

Try it

  • "What's the current H100 on-demand index?"
  • "Compare FLOPS-H100-OD vs FLOPS-B200-OD over the last 30 days."
  • "Verify the receipt for FLCI-H100 from 2026-05-15."
  • "What methodology version backs the current FLOPS-H100-SPOT publication?"
3 REST — any HTTP client, any language 5 min

The lowest-level path. Auth-free Track-D endpoints serve LIVE public indices with no signup. Authenticated partner endpoints unlock the full catalog plus history, custom indices, and audit substrate.

Auth-free (public)

curl https://app.flopsindex.com/v1/price/FLOPS-H100-OD
{"value": 6.155, "tier": "LIVE", "confidence": "HIGH",
 "unit": "USD/GPU-hr", "as_of": "2026-05-18T13:00:00Z",
 "methodology_version": "flops-h100-od@v0.9"}

curl https://app.flopsindex.com/v1/ts/FLOPS-H100-OD?range=7d
{"slug": "FLOPS-H100-OD", "range": "7d", "count": 168, "points": [...]}

curl https://app.flopsindex.com/v1/search?q=H100
{"hits": [{"slug": "FLOPS-H100-OD", ...}, ...]}

Partner tier (X-FLOPS-Api-Key)

curl -H "X-FLOPS-Api-Key: $FLOPS_API_KEY" \
     https://app.flopsindex.com/v1/catalog
# Full catalog, all families, methodology pins

curl -H "X-FLOPS-Api-Key: $FLOPS_API_KEY" \
     "https://app.flopsindex.com/v1/derived/spread?a_gpu_model=H100&a_index_type=on_demand&b_gpu_model=B200&b_index_type=on_demand&range=30d"
# Time-aligned spread + z-score + percentile rank

curl -H "X-FLOPS-Api-Key: $FLOPS_API_KEY" \
     "https://app.flopsindex.com/v1/derived/compute-margin?sku=h100_sxm5®ion=us_west"
# Live spark-spread per (SKU, region)

Python SDK (zero deps, stdlib only)

pip install flopsindex

from flopsindex import FlopsClient
c = FlopsClient(api_key="...")
print(c.price("FLOPS-H100-OD"))         # public
print(c.catalog())                       # partner
print(c.spread("H100", "on_demand", "B200", "on_demand", range="30d"))
Headline indices to try first 1 min
SLUGWHAT IT MEASURES
FLOPS-H100-ODH100 SXM5 on-demand $/GPU-hr — the canonical compute reference
FLOPS-H100-SPOTH100 spot/marketplace price — preemptible counterparty
FLOPS-B300-ODBlackwell B300 on-demand — frontier silicon settlement
FLOPS-H100-DEPINH100 via decentralized GPU networks (Akash / io.net / Targon)
FLOPS-llama-3.1-70b-INFERENCE_OUTPUTOutput token price (USD/1k tokens) across hosted providers
FLCI-H100-us_westFull-lifecycle cost index per region (capex + power + ops)
? Common questions
How do I get an API key?
If you're a pilot partner, your operator created your account via /admin and shared the credentials. If you're not yet a pilot partner, email team@flopsindex.com with your use case — turnaround is typically same-day.
What's the difference between SETTLEMENT and LIVE INTRADAY?
SETTLEMENT is a 24h-window publication suitable for mark-to-market, covenant true-ups, and contract pricing. LIVE INTRADAY is a 1-hour rolling reference for agents and intraday workflows. Both use the same math — different observation windows. Sustained spreads >10% indicate the settlement reference is lagging; the F4 panel surfaces both.
What does "k-anonymity ≥ 3" mean?
Every settlement-grade published value reflects at least 3 independent source quotes. Below-3 ticks exist in the partner-tier inspection table but never appear on the public surface. This protects contributor confidentiality (no single source can be back-derived from the published value) and aligns with IOSCO Principle 7.
How do I verify a published value?
Every oracle_prices row carries an SHA-256 observations_hash + computation_proof JSON. The full audit trail is one request away: GET /v1/audit/recompute/{run_id}. The Recompute Audit panel on the F13 GOVRN dashboard tab shows the daily replay.
What's the publication cadence?
SETTLEMENT family: daily, 24h-window mark. LIVE INTRADAY: hourly. CLRI-FWD (forward curve): hourly. ITPI (inference tokens): hourly. Site-intelligence reference data: per-source (daily to quarterly). Pilot partners receive a weekly published index under contract — the upstream APIs run more often, but the contractual covenant is weekly.
What does the methodology version control?
Each published value pins to a methodology version (e.g. flci-h100@v0.9). A methodology change never silently rewrites history — the new version pins at the change moment and old values keep their old version. Methodology versions are immutable; the change log lives at /v1/methodology/{id}/versions.

Ready to wire it up?

Email us Open the dashboard Browse the public catalog