Integration boundaries

Use the registered HTTP API against the matching deployed Helm version. The current API and database evolve together; it is not an unrestricted table-access interface.

Available boundary

The endpoint catalog lists registered methods, paths and scopes. Request validation, ownership and domain rules apply in addition to those rows. Some first-party read branches are not exposed to API-token clients.

Historical resources and direct database writes are not the recommended integration path. A database function’s existence does not make it a public endpoint.

Planned capabilities

• Complete-history export and self-service account deletion.
• Advanced Activity searching and filtering.
• A supported hosted assistant/MCP transport.
• Broader integrations and revocable statement sharing.

export:finance is reserved permission, not evidence of a mounted export facility. The MCP status page explains what the generated manifest does today.

Deployment-dependent services

For your own installation, configure provider mail, worker invocation and reference-rate refresh explicitly. Test the actual transport before depending on it. A successful recovery request does not prove email delivery, and a worker file does not establish a schedule.

Keep consumer behavior conservative: preserve unavailable states, use scoped credentials and support explicit recovery. See the public roadmap for product direction without delivery promises.