canonical: https://jentic.com/apis/ntropy.network/main # Ntropy Network Ntropy Transaction API v1 The Ntropy Transaction API classifies and enriches bank transactions for consumer and business accounts. The v1 spec exposes batch retrieval endpoints for previously submitted classification jobs, returning structured merchant, category, and intent labels for each transaction. Used by fintechs, neobanks, and accounting tools to turn raw bank-feed strings into clean, queryable transaction data without building in-house enrichment pipelines. ## For AI agents Retrieve enriched and classified consumer or business transaction batches from Ntropy through 2 endpoints. Public spec; production use requires Ntropy credentials. ## Scope Does not handle bank account aggregation, payment initiation, or KYC checks - use for transaction classification and enrichment only. ## Capabilities - Retrieve a batch of business transaction classification results by batch ID - Retrieve a batch of consumer transaction classification results by batch ID - Surface merchant identification, category labels, and transaction intent for downstream apps - Power transaction categorization in personal finance and accounting tooling - Feed enriched transaction data into reconciliation and underwriting workflows ## Use cases ### Personal Finance Transaction Categorization Personal finance apps submit raw bank-feed transactions to Ntropy and later retrieve enriched results via GET /classifier/consumer/batch/{id}. The response includes merchant identification, category labels, and recurring-payment flags so the app can group transactions in the user's spending UI without building classification models in-house. Example prompt: Call GET /classifier/consumer/batch/{id} for a queued batch, parse merchant and category fields, and update the user's spending dashboard ### Business Banking and Accounting Reconciliation Accounting platforms and SMB banking tools enrich business transaction feeds for reconciliation. GET /classifier/business/batch/{id} returns structured business-context labels - merchant entity, B2B category, and transaction nature - that flow into general-ledger postings, automatic vendor matching, and expense categorization rules. Example prompt: Call GET /classifier/business/batch/{id} for a posted batch and route each enriched transaction to the matching general-ledger account ### AI Agent Bank Feed Cleanup via Jentic Personal-finance AI agents use Jentic to retrieve enriched Ntropy batches and answer user questions about spending categories, recurring charges, and merchants. The agent calls /classifier/consumer/batch/{id} to pull cleaned data and produces a summary the user can act on, without holding Ntropy credentials in its prompt. Example prompt: Use Jentic to search 'Ntropy consumer batch results', load /classifier/consumer/batch/{id}, and execute with the batch ID ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /classifier/consumer/batch/{id} | Retrieve consumer transaction classification batch results | | GET | /classifier/business/batch/{id} | Retrieve business transaction classification batch results | ## Key resources - **Consumer Classifier** — Retrieve consumer transaction enrichment batch results - **Business Classifier** — Retrieve business transaction enrichment batch results ## Why Jentic - **Setup:** Wiring the Ntropy Transaction API by hand means constructing batch-classification requests against api.ntropy.network and mapping the consumer and business batch operations yourself. Through Jentic you install once, import the Ntropy Transaction API from the API Directory, store the account key once, and your agent calls it. - **Permission scoping:** Ntropy puts the batch id in the URL path (/classifier/consumer/batch/{id}), so a rule can pin your agent to one batch. Both operations here are read-only retrievals, so you choose whether the agent reads consumer batches, business batches, or both. - **Credential handling:** Your Ntropy account 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 'retrieve enriched bank transactions', and Jentic returns the matching consumer or business batch operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plaid** — Bank account aggregation and raw transaction feeds, often enriched downstream by Ntropy - **MX** — Transaction enrichment plus account aggregation in one platform - **TrueLayer** — European open banking aggregation that pairs well with Ntropy's enrichment ## FAQ ### What authentication does the Ntropy Transaction API use? The published v1 spec does not declare a security scheme on these endpoints, but production use of api.ntropy.network requires an Ntropy account and credentials issued at https://ntropy.network. Through Jentic, those credentials live in the vault and are injected at execution time so they never appear in agent prompts. ### Can I retrieve classified business transactions in batches with the Ntropy Transaction API? Yes. GET /classifier/business/batch/{id} returns the classification results for a previously submitted business batch, including merchant entity, B2B category, and structured transaction labels. ### What are the rate limits for the Ntropy Transaction API? Ntropy publishes account-tier rate limits on its developer site at api.ntropy.network rather than in this spec; limits typically scale with plan size. Long-running batch retrievals should be polled with backoff to stay under the per-account allotment. ### How do I retrieve consumer batch results through Jentic? Search Jentic for 'Ntropy consumer batch results', load the GET /classifier/consumer/batch/{id} schema, and execute with the batch ID returned by the submit step. The flow is pip install jentic, then await client.search, load, and execute. ### Is the Ntropy Transaction API free? Ntropy offers tiered pricing based on enrichment volume; pricing details are on the Ntropy website. There is generally a sandbox tier for evaluation before production usage commitments. ### Can I limit what my agent is allowed to do with the Ntropy Transaction API? Yes. Jentic One is self-hosted, so your own rules decide which Ntropy operations your agent may call and which credentials it may use. Because both endpoints here are read-only batch retrievals, you can allow the agent to read consumer batches via GET /classifier/consumer/batch/{id}, business batches via GET /classifier/business/batch/{id}, or both. Since the batch id sits in the URL path, a rule can also pin the agent to a single batch.