Data from every bank in one API. And in your AI assistant.
A REST API with OpenAPI 3.1 for accounts, balances, transactions, payments and investments across all your banks. Plus an MCP server so Claude, ChatGPT and Microsoft Copilot can query your treasury.
One integration instead of one per bank.
One API, every bank
The same contract for Itaú, Bradesco, Santander and every other bank in the group.
AI-ready
An MCP server and OpenAPI 3.1 that assistants and agents read on their own, with no integration code to write.
Managed connectivity
Certificates, bank outages and reconnections handled by Datanomik, not by your team.
From the first key to data in your system.
Three steps, in sandbox or production
1. Connect
Generate a key in your account and make your first call with HTTP Basic. The sandbox comes with unlimited sample data and needs no bank credentials.
2. Consume
Accounts, balances, transactions, payments, collection reports (francesinhas) and investments from every bank in the same format, with the same pagination on every endpoint.
3. Converse
Connect the MCP server to Claude, ChatGPT or Microsoft Copilot and ask in plain language. The assistant queries Datanomik and answers with the number.
Everything the data team needs to integrate.
API, MCP, documents and security, with bank connectivity taken care of by Datanomik.
REST API with OpenAPI 3.1
Every path and operation described in a single file, with ready-to-copy examples. Generate the client in your language or let an agent read the contract.
MCP server
Claude, ChatGPT, Microsoft Copilot or any MCP-compatible client can query balances, transactions, payments, investments and debt. Authentication via OAuth 2.1 or API key.
Receipts and documents via API
The PDF receipt for every payment and every Pix, the collection reports and the balance history, fetched by your system without anyone downloading a file.
Connection health
The status of each bank, the time of the last reading and the certificates about to expire. When a bank goes down, Datanomik retries and lets you know if it needs you.
Security and role-based access
HTTPS on every call, separate keys per environment, role-based permissions and data handled under the LGPD (Brazil's data protection law), with practices aligned with ISO/IEC 27001.
What changes in practice
One integration for every bank
No certificates to maintain bank by bank
PDF receipts fetched through the API
Treasury queried in plain language through your assistant
Sandbox with unlimited sample data
OpenAPI 3.1 ready to generate clients
Frequently asked questions
What data is available through the API?
Institutions, accounts and account holders, balances and consolidated position, categorized transactions, investments and movements, payments, Pix, settled boletos and PDF receipts, plus cash flow records.
How does authentication work?
The API uses HTTP Basic with the keys generated in your Datanomik account. The MCP server accepts the X-Api-Key header or OAuth 2.1 with PKCE.
Which AI assistants work with the MCP server?
Claude, ChatGPT and Microsoft Copilot through Copilot Studio, plus any client compatible with the Model Context Protocol. The server lives at mcp.datanomik.com/mcp.
Is there a test environment?
Yes. The sandbox has unlimited sample data and doesn't require real bank credentials. When you're ready, just switch to the production key.
Does the API execute payments?
No. Bank data is read-only: balances, transactions, payments and receipts the banks have already recorded. Payments are still made at your bank or in your ERP.
How do you handle data security?
Encrypted connections, keys per environment, role-based permissions and handling under the LGPD, with security practices aligned with ISO/IEC 27001. The details are on the Security page.
Ready to transform your treasury?
Fill out the form and our team will get in touch shortly.
Allan Andrade
Datanomik Treasury Manager
