canonical: https://jentic.com/apis/afterbanks.com/afterbanks # Afterbanks API The Afterbanks API aggregates bank account and transaction data across banks. It lists the connection forms for supported banks, authenticates a user's bank login, and returns their accounts and transaction history in a normalized format, so applications can pull financial data without building a separate integration for each bank. ## For AI agents List supported bank connection forms, authenticate a user against their bank, and retrieve their accounts and normalized transaction history through a single aggregation API. ## Scope Does not initiate payments, issue cards, or provide credit scoring. Use for bank account and transaction aggregation only. ## Capabilities - List the connection forms available for supported banks - Authenticate a user's bank login and retrieve their accounts - Pull account balances and transaction history in a normalized format - Aggregate financial data across multiple banks through one API ## Use cases ### Agent-Driven Account Aggregation An AI agent onboarding a user can list the supported banks, guide the bank connection, and return the user's accounts and balances in one normalized shape. This replaces per-bank scraping or bespoke integrations with a single call. Through Jentic the agent discovers the aggregation operation by intent and runs it with the service key injected at call time. Example prompt: Connect the user's bank and return their account balances ### Transaction Analysis A financial agent can pull a connected account's transaction history in a normalized format and categorize spending, detect recurring charges, or feed a budgeting model. Because the data is consistent across banks, the same logic works regardless of the underlying institution. The agent reads only the accounts the user has connected. Example prompt: Pull the last 90 days of transactions for the connected account and categorize spending ### Multi-Bank Financial Overview For users with accounts at several banks, an agent can aggregate balances across all connected institutions into a single overview. This gives a consolidated financial picture without the user logging into each bank. The agent refreshes the data on demand when the user asks. Example prompt: Aggregate balances across all of the user's connected banks into one summary ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/forms` | List connection forms for supported banks | | POST | `/me` | Retrieve the authenticated user's accounts | | POST | `/serviceV3` | Fetch accounts and transactions for a connected bank | ## Key resources - **Bank forms** — The connection forms describing how to link each supported bank - **Accounts** — A connected user's bank accounts and current balances - **Transactions** — Normalized transaction history for connected accounts ## Why Jentic - **Setup:** Wiring the Afterbanks API by hand means registering for a service key, attaching it to every request, and handling the bank-connection flow and normalized response format yourself. Through Jentic you install once, import Afterbanks from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Afterbanks carries the connection target in the request body rather than the URL path, so rules bound which operations the agent may call rather than which bank. You can allow reading accounts and transactions while withholding other operations. - **Credential handling:** Your Afterbanks service key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'aggregate bank accounts' or 'pull transaction history', and Jentic returns the matching Afterbanks operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Plaid** — Plaid aggregates bank accounts and transactions with strong US coverage. - **TrueLayer** — TrueLayer provides open banking data and payments across Europe. - **Nordigen** — Nordigen offers free open banking account and transaction data across the EU. ## FAQ ### Is there an Afterbanks MCP server? You don't need an MCP server to connect your agent to the Afterbanks API. Jentic imports it from the API Directory, stores your service key once, and your agent aggregates accounts and transactions directly. No extra server sits in the agent's context. ### Can I limit what my agent is allowed to do with the Afterbanks API? Yes. Afterbanks exposes a small set of operations for listing banks, authenticating, and pulling data, and you choose which the agent may call. You can allow it to read accounts and transactions while withholding anything else. Requests carry the target in the body rather than the URL path, so rules bound which operations the agent may use. Every call is logged. ### What authentication does the Afterbanks API use? The Afterbanks API authenticates with a service key that identifies your account on each request. Through Jentic the service key is stored encrypted by your own Jentic One instance and injected when the agent makes a call, so it never appears in the agent's prompt or logs. ### Can my agent pull transactions from multiple banks with the Afterbanks API? Yes. Afterbanks normalizes data across the banks it supports, so an agent can connect several of a user's banks and retrieve their accounts and transactions in one consistent format. ### What are the rate limits for the Afterbanks API? The OpenAPI spec does not specify rate limits. Check the Afterbanks documentation for the current limits before scaling an agent's data pulls. ### How do I aggregate a user's accounts with the Afterbanks API through Jentic? Search Jentic for 'aggregate bank accounts' and it returns the Afterbanks operation with its input schema. Store your service key once, then your agent connects a bank and reads back accounts and transactions. To run it on your own infrastructure, install Jentic One from its GitHub repo.