Developers
What you can build on, today.
Chainage has a documented REST API and read-only API keys, so reporting systems can follow inspections as they are decided. Fennec exports its results as JSON and CSV. The fz command-line tool and the MCP server are paused, and this page says why.
01Chainage API · live
Read the inspections, as they are decided.
Read-only by design: an integration can follow the work, never change it.
- Base URL
https://chainage-api.fluidzero.ai- Reference
- Interactive docs at chainage-api.fluidzero.ai/docs, and the OpenAPI 3.1 document at /openapi.json. Both are public.
- API keys
- An organization admin creates them in Chainage, under Organization settings, Integrations. A key is shown once, stored only as a hash, can be limited to one project and given an expiry, and can be revoked.
- What a key can do
- Read inspections and their results: list a project's inspections, and read one by its number. Nothing else. Any other route answers 403, and a revoked or expired key 401.
- Paging and sync
- Lists are cursor-paged, up to 200 at a time. Filter by status, layer, side, a chainage range, or updatedSince to fetch only what changed.
- Responses
- Every response carries success, data or error, and a request id to quote when you report a problem.
- Webhooks
- Built, signed and documented, but not yet switched on. Until they are, poll with updatedSince.
Approved inspections changed since 1 October
curl "https://chainage-api.fluidzero.ai/v1/projects/$PROJECT_ID/rfis?status=APPROVED&updatedSince=2026-10-01T00:00:00Z" \
-H "X-Api-Key: $CHAINAGE_API_KEY"
{
"success": true,
"data": { "items": [ … ], "nextCursor": "eyJ0cyI6…" },
"meta": { "requestId": "…", "serverTime": "…" }
}02Fennec
Results that leave with their sources.
- Exports
- A run's results download as JSON or CSV: one record per document, named by its file, with its status and extracted fields. The page behind each field is shown in Fennec itself.
- API
- Fennec's API serves its own web application and is not offered for integration yet.
03fz CLI and MCP server · paused
Paused, and said plainly.
- Status
- Paused. Both were built for the API of an earlier version of Fennec, which has been retired, so they do not connect today.
- fz CLI
- Version 0.2.0 of fluidzero-cli still installs from PyPI. Do not build on it; it cannot reach a server.
- MCP server
- The hosted server at mcp.fluidzero.ai answers, but has no API behind it.
- What changes this
- This page will say so when either connects to Fennec as it runs today.
Next step
Need to connect something else?
Tell us what you want to connect and what it should read. We will say plainly whether it can be done today.