API Roadmap
What is planned for the GatiFlow API, in order, without dates. What has already shipped is in the changelog, and an item leaves this page when it ships. Nothing here changes the published contract until it ships under the versioning policy.
Next
A lint ruleset for our own contract. The Spectral rules the OpenAPI document is held to, run on every change and published beside the contract.
A vocabulary of the terms the API uses. Signal, trend, confidence, corroboration, source authority: each defined once, in a machine-readable file the contract points to.
A conformance declaration. The standards the contract follows, listed as data rather than described in prose.
Agent instructions written by us. An Agent Skill for working with the report, and an x-agentic-access classification of every operation.
Later
An MCP server. The published operations exposed as Model Context Protocol tools, at a public endpoint.
OAuth 2.1 beside API keys. So an agent can obtain a token scoped to the person it acts for, instead of carrying a long-lived key.