For Developers

Build on top of DoubleM financial data.

Use the REST API for structured application integrations, or connect the MCP server so AI assistants can read reports and perform approved finance actions through tools.

Authentication first

External integrations should use a DoubleM API key token in the Authorization header. First-party clients may use a Supabase JWT.

Owner-scoped data

Every route and tool operates on the authenticated user account. Integrations should never submit user_id manually.

Predictable envelopes

Responses use consistent success and error shapes so client apps can build one shared handler.

Review side effects

Account debits, card transactions, bill payments, loan payments, and MCP tool writes should be user-approved in your UI.