Integration

Ntropy integration

Ntropy enriches bank transactions: from a raw transaction description it identifies the merchant (counterparty), payment intermediaries and location, assigns a category, and finds recurring payments in an account holder's history. Enrich one transaction or a batch of up to 24,960, manage account holders and their transaction history, extract transactions and balances from bank statement PDFs, resolve a business name or website to an entity, customize category sets and labelling rules, report wrong results and manage webhooks. Transactions, account holders and bank statements are personal financial data; bank account numbers are withheld from bank statement results and the webhook token is never returned. The legacy v2 routes are not exposed. Authentication is an API key from the Ntropy dashboard, sent in the X-API-KEY header.

Connect Ntropy How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ntropy.Built from the 40 Ntropy tools below, on the connection you add once.

What you can do with Ntropy

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transaction, 6 operations

assign_transactionAssign transactionPOSTAgents: ask firstMoves a transaction to another account holder of the same type (consumer or business) and returns the updated transaction. This changes which history the transaction counts in.
delete_account_holder_transactionsDelete account holder transactionsPOSTAgents: ask firstPermanently deletes up to 1,000 of an account holder's transactions by id; ids of another holder's transactions are ignored. They leave every listing, history and recurrence result. Cannot be undone.
delete_transactionDelete transactionDELETEAgents: ask firstPermanently deletes one transaction from Ntropy's systems. This cannot be undone.
enrich_transactionEnrich transactionPOSTAgents: ask firstEnriches one bank transaction (billed per transaction): returns the counterparty, intermediaries, location and category found from its description. The answer holds only the enriched fields and the id; read the full record with get_transaction.
get_transactionGet transactionGETAgents: ask firstReturns one enriched transaction with its original fields (description, date, amount, entry_type, currency), the entities, categories and location found, and its account holder. Personal financial data.
list_transactionsList transactionsGETAgents: ask firstLists enriched transactions, most recent first, optionally only those of one account holder. Each item has the original fields plus entities, categories and location (personal financial data). Page with next_cursor.

Bank statement, 5 operations

delete_bank_statementDelete bank statementDELETEAgents: ask firstPermanently deletes a bank statement and its extraction results. This cannot be undone.
get_bank_statementGet bank statementGETAgents: ask firstReturns a bank statement's processing status (processing, completed or error), file name, page count and size, and the error if extraction failed. Poll it after upload_bank_statement.
list_bank_statementsList bank statementsGETAgents: ask firstLists submitted bank statements, most recent first, with their file name, status, page count and any error. Page with next_cursor.
upload_bank_statementUpload bank statementPOSTAgents: ask firstUploads a bank statement PDF for extraction and returns its id and status (processing). Call get_bank_statement until status is completed, then get_bank_statement_results; verify_bank_statement reads page one sooner.
verify_bank_statementVerify bank statementPOSTAgents: ask firstReads the first page of an uploaded bank statement right away: institution, statement period, account holder (type, name, address) and accounts with balances. Personal data; account numbers are withheld.

Rule, 5 operations

create_ruleCreate rulePOSTAgents: ask firstAppends one rule to the API key's personalization ruleset; it then changes the fields of every matching enrichment result. Returns its index.
delete_ruleDelete ruleDELETEAgents: ask firstDeletes the rule at the given position of the personalization ruleset; later rules move up one position.
list_rulesList rulesGETAgents: ask firstReturns the API key's personalization ruleset: the list of rules (actions and conditionals) applied to every enrichment result, in order. A rule's position in the list is the id that update_rule and delete_rule take.
replace_rulesReplace rulesPOSTAgents: ask firstReplaces the whole personalization ruleset of the API key with the given list of rules; every existing rule is discarded. Read the current rules with list_rules first if any should be kept.
update_ruleUpdate rulePATCHAgents: ask firstReplaces the rule at the given position of the personalization ruleset with a new rule and returns its index. The previous rule at that position is discarded.

Webhook, 5 operations

create_webhookCreate webhookPOSTAgents: ask firstCreates a webhook: Ntropy will POST to the url when one of the chosen events occurs (batch, bank statement or report status changes). At most 10 webhooks per organization. Returns it without its token.
delete_webhookDelete webhookDELETEAgents: ask firstDeletes a webhook; Ntropy stops sending it events.
get_webhookGet webhookGETAgents: ask firstReturns one webhook: url, subscribed events, enabled flag and creation time (its token is not returned).
list_webhooksList webhooksGETAgents: ask firstLists the organization's webhooks with url, subscribed events, enabled flag and creation time (tokens are not returned).
update_webhookUpdate webhookPATCHAgents: ask firstUpdates a webhook's url, events, token, signing secret or enabled flag; fields left out keep their current value. Setting enabled to false stops deliveries.

Account holder, 4 operations

create_account_holderCreate account holderPOSTAgents: ask firstCreates an account holder (a consumer or a business) whose transactions form one history, used for categorization and recurrence. Returns it with its creation time.
delete_account_holderDelete account holderDELETEAgents: ask firstPermanently deletes an account holder and every transaction in its history. This cannot be undone.
get_account_holderGet account holderGETAgents: ask firstReturns one account holder: id, type (consumer or business), name, custom category set and creation time.
list_account_holdersList account holdersGETAgents: ask firstLists account holders, most recent first, with id, type (consumer or business), name, custom category set and creation time. Page with next_cursor.

Report, 4 operations

create_reportCreate reportPOSTAgents: ask firstReports a transaction whose enrichment is wrong, so Ntropy investigates it. Returns the report with status open; it later moves to pending, then resolved or rejected (with a reason).
delete_reportDelete reportDELETEAgents: ask firstDeletes a report of a wrong enrichment result.
get_reportGet reportGETAgents: ask firstReturns one report: the transaction, the description and fields reported, its status (open, pending, resolved or rejected) and the rejection reason if rejected.
list_reportsList reportsGETAgents: ask firstLists reports of wrong enrichment results, most recent first, with status (open, pending, resolved or rejected) and rejection reason. Page with next_cursor.

Batch, 3 operations

create_batchCreate batchPOSTAgents: ask firstSubmits up to 24,960 transactions for asynchronous enrichment (billed per transaction) and returns the batch with its id and status. Call get_batch until status is completed or error, then get_batch_results.
get_batchGet batchGETAgents: ask firstReturns a batch's status (processing, completed or error), progress (transactions processed) and total. Poll it after create_batch; when completed, read the output with get_batch_results.
list_batchesList batchesGETAgents: ask firstLists submitted enrichment batches, most recent first, with their status (processing, completed or error) and progress. Page with next_cursor.

Category set, 3 operations

get_category_setGet category setGETAgents: ask firstReturns a category set: the incoming and outgoing category labels transactions can receive. consumer and business are the default sets; any other id is a custom set made with set_category_set.
reset_category_setReset category setPOSTAgents: ask firstResets a category set to its original values, discarding the custom categories set on it with set_category_set. Returns the resulting set.
set_category_setSet category setPOSTAgents: ask firstCreates or overwrites a custom category set with the given incoming and outgoing categories. Transactions matching none are categorized 'not enough information'. Overwrites any set with that id.

Entity, 2 operations

get_entityGet entityGETAgents: ask firstReturns an entity (a business found in transactions) by id: name, website, logo, merchant category codes, parent entity and location; phone number, tax number and NAICS code only on plans with that premium feature.
resolve_entityResolve entityPOSTAgents: ask firstResolves a business name or a website to an Ntropy entity: id, name, website, logo, merchant category codes, parent and location. Pass name or website, not both; a call with name is billed like a transaction.

Bank statement result, 1 operation

get_bank_statement_resultsGet bank statement resultsGETAgents: ask firstReturns the accounts extracted from a bank statement whose status is completed: account name, period, opening and closing balances, totals and every transaction with its running balance. Account numbers are withheld.

Batch result, 1 operation

get_batch_resultsGet batch resultsGETAgents: ask firstReturns a finished batch's enriched transactions in the order they were sent, with the batch status and total. Results exist only once get_batch reports status completed (personal financial data).

Recurring group, 1 operation

find_recurring_groupsFind recurring groupsPOSTAgents: ask firstFinds recurring payments (subscriptions, salaries, bills) in an account holder's transaction history: one group per pattern with periodicity, amounts, date range, counterparty, category and transaction ids.

Use Ntropy from Claude Code, Cursor or Codex

Connect Ntropy in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ntropy operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ntropy

Create your workspace
Sign up free. Nothing to install.
Connect Ntropy once
Add your Ntropy connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.