The read API.

Every figure a screen shows, as JSON. Read-only: nothing here approves, changes or writes, and every number is the engine's, never estimated.

Authorization

One bearer, two kinds: the organization's key from Settings → Claude Code and Cursor, or the token a person's sign-in gives an app through the MCP server.

A key reads one organization. A token reads one organization as one person.

curl https://app.valistry.ai/api/v1/estate?days=30 \
  -H "Authorization: Bearer vly_mcp_…"

Resources

/api/v1/estate: Total, sources, coverage, unallocated, realizable now, governed share, the spike, the month at this pace. Parameters: days.
/api/v1/spend: Spend by one dimension, each group's share and tokens; against the period before when asked. Parameters: by · days · compare.
/api/v1/findings: Every finding with its evidence, the change to make, how it is verified, and where it is tracked. Parameters: status: open · approved · verified · all.
/api/v1/ledger: Every decision, with the saving expected on approval and the saving measured after.
/api/v1/policies: Every policy with its mode, owner, the metric against its threshold, and the envelope at this pace. Parameters: days.
/api/v1/alerts: What watches raised in the window, with its state and whether it was sent. Parameters: days · state.
/api/v1/ask: A question in plain words, answered with the figure, the plan that produced it and the evidence. Parameters: q · days.
POST /api/v1/records: Your own records, in the shape every connector writes: a bill, an export, a vendor we have no connector for. Needs the push key, not the read key.

Every response carries the window it was read over. A Starter organization gets what its screens show: the what, never the who or the change.

On Enterprise, the same figures are also pushed nightly to an endpoint you name, signed.

The MCP server

The same seven tools, as a Model Context Protocol server at the same address, for Claude Code, Cursor and Claude. A question in plain words becomes a typed plan, the plan runs over the engine, and the figure comes back with its evidence. The chat signs in; the editor takes the key.

Endpoint: https://app.valistry.ai/api/mcp
Transport: Streamable HTTP, JSON-RPC by POST, stateless.
Sign-in: OAuth 2.1 with PKCE; the server registers clients itself and names its metadata on a 401.
Tools: ask · spend · estate · findings · ledger · policies · alerts