# Roadmap

Intentions, not contracts. Nothing on this page answers yet, and nothing anywhere else in these docs is described in the future tense.

> Everything on this page is an intention, not a contract. No endpoint here answers yet, and none of it is described in the present tense anywhere else in these docs.

| Item | What it will be, and why it is not here yet |
| --- | --- |
| The /v1 REST façade | Resource paths and bearer keys over the same engine. Deferred to before the first external client: with zero integrations today, changing later breaks nobody, while documenting a façade that does not answer breaks everybody. |
| Dated versioning (Sidaxis-Version) | A change policy worth publishing once there is a client to protect. |
| Published rate limits and rate-limit headers | Real ceilings, measured, with headers on every response. Today only the alias endpoint's limits are published, because those are the only ones we are prepared to promise. |
| Cursor pagination on mandate reads | mandate-get currently returns a list by effective status, and a single-mandate read includes the last 100 consumptions. |
| A public status page with measured availability and targets | No SLA is published until it is measured. |

## Not on this page

The MCP server. It is in production at `https://api.sidaxis.com/functions/v1/mcp` with nine tools — see [MCP](/mcp).

> The rule that produced this page: a documented endpoint that does not answer is worse than an absent one. Nothing moves off this page until it responds.