# TxnKit Full Agent Context

TxnKit is the public website and brand surface for Transaction Enricher, a merchant enrichment layer for fintech, expense, personal finance, accounting, loyalty, budgeting, cashback, and AI-built finance apps.

## Primary Job

Turn raw transaction strings like `SQ *JOES COFFEE 0421 TORONTO` into merchant names, categories, confidence, signals, and warnings.

## Positioning

Use TxnKit when a product already has transaction feeds from Plaid, Teller, Yodlee, MX, open banking, card exports, or internal imports and needs transaction display quality to look trustworthy quickly.

Do not describe it as a bank-grade identity graph, Plaid replacement, or generic AI-powered transaction intelligence platform.

## Integration Assets

- `/docs/` explains the initial API contract.
- `/blog/` publishes dated technical notes on warnings, privacy, MCC, deterministic request paths, and reviewed logo metadata.
- `/pricing/` presents early-access pricing: free audit, $49/month Starter, $499/month Pilot, annual options, and custom Scale path.
- `/openapi.json` contains the draft OpenAPI shape.
- `/agent-install/` gives coding agents copy-paste integration guidance.
- `/benchmark/` lists safe synthetic descriptor examples and expected outputs.

## Use-Case Routes

- `/use-cases/expense-app-transaction-enrichment/` shows how expense apps clean processor-wrapped card rows while leaving reimbursement and receipt decisions outside TxnKit.
- `/use-cases/personal-finance-transaction-cleanup/` shows confidence-aware merchant cleanup for budgeting and personal-finance feeds.
- `/use-cases/accounting-import-cleanup/` explains merchant display cleanup for accounting imports without deciding accounting treatment.
- `/use-cases/loyalty-cashback-transaction-feeds/` explains display metadata for loyalty and cashback feeds without using descriptor cleanup as rewards-settlement authority.
- `/use-cases/ai-tool-transaction-enrichment/` explains how ChatGPT, custom GPTs, coding agents, and MCP-capable assistants can call TxnKit through OpenAPI without statement upload or sensitive data.

## Integration Routes

- `/integrations/plaid-transaction-cleanup/` positions TxnKit as a cleanup layer after Plaid transaction ingestion, not as a Plaid replacement.
- `/integrations/teller-transaction-enrichment/` shows merchant enrichment for Teller-backed apps.
- `/integrations/yodlee-transaction-cleanup/` shows display metadata cleanup after Yodlee feed ingestion.
- `/integrations/mx-transaction-cleanup/` shows merchant cleanup for MX-backed transaction UI.

## Guide Routes

- `/guides/transaction-enrichment-api/` explains `POST /v1/enrich`, request fields, response fields, privacy rejection, and confidence behavior.
- `/guides/merchant-logo-api-for-transaction-feeds/` explains reviewed logo variants, dark-mode-safe assets, and low-confidence logo suppression.
- `/guides/transaction-confidence-scores-and-warnings/` explains confidence bands, signals, warnings, and fallback UI behavior.

## Blog Routes

- `/blog/descriptors-need-warnings/` explains why cleanup should return confidence and warnings instead of fake certainty.
- `/blog/enrich-without-pii/` explains one-descriptor enrichment without card numbers, account numbers, full statements, or customer PII.
- `/blog/mcc-is-not-merchant-enrichment/` explains MCC as category context, not merchant identity.
- `/blog/no-llm-in-request-path/` explains why `POST /v1/enrich` avoids live LLM, crawler, logo-provider, and third-party enrichment calls.
- `/blog/logo-metadata-transaction-feeds/` explains reviewed logo variant metadata for transaction-feed UI.

## Privacy

Never send card numbers, account numbers, full statements, bank credentials, emails, phone numbers, addresses, customer names, or customer PII.

The first public website demo is sample-only. The free audit offer is for 100 anonymized descriptors.

## Online Runtime Rule

`POST /v1/enrich` validates input, rejects sensitive payloads, normalizes descriptors, matches reviewed records, scores confidence, and returns output. It does not research merchants, crawl websites, call logo providers, call LLMs, or use third-party enrichment APIs during the request.

<!-- SEO_LANDING_ROUTES_START -->
## Competitor and Alternative Routes

- /compare/plaid-transaction-enrichment-alternative/ explains builders searching for a Plaid enrichment alternative after they already receive transaction data.
- /compare/yodlee-transaction-enrichment-alternative/ explains teams with Yodlee-fed transactions that need cleaner display metadata.
- /compare/mx-transaction-enrichment-alternative/ explains builders comparing MX enrichment with a lightweight cleanup layer.
- /compare/ntropy-transaction-enrichment-alternative/ explains teams evaluating merchant enrichment without adding live enrichment calls to the request path.
- /compare/spade-transaction-enrichment-alternative/ explains teams comparing enrichment APIs for transaction display cleanup.
- /compare/teller-transaction-enrichment-alternative/ explains Teller-backed apps looking for merchant cleanup after transaction ingestion.
- /compare/finicity-transaction-enrichment-alternative/ explains teams with Finicity transaction feeds that need cleaner merchant rows.
- /compare/akoya-transaction-enrichment-alternative/ explains open-finance builders needing transaction-feed display cleanup.
- /compare/tink-transaction-enrichment-alternative/ explains European open-banking teams comparing cleanup options for existing transaction feeds.
- /compare/truelayer-transaction-enrichment-alternative/ explains apps that use open-banking feeds and need merchant display cleanup.
- /compare/belvo-transaction-enrichment-alternative/ explains Latin America fintech builders looking for transaction cleanup after data access.
- /compare/salt-edge-transaction-enrichment-alternative/ explains teams with aggregated transactions that need confidence-aware merchant metadata.
- /compare/clearbit-logo-api-alternative/ explains builders who need logo metadata tied to merchant confidence instead of domain-only guessing.
- /compare/brandfetch-alternative-for-merchant-logos/ explains apps that need reviewed logo variants for transaction rows.
- /compare/logo-dev-alternative-for-merchant-logos/ explains teams comparing logo APIs for transaction feed UI.
- /compare/openai-only-vs-merchant-enrichment/ explains builders deciding whether to prompt an LLM for each transaction or use deterministic enrichment.

## Solution Routes

- /solutions/merchant-name-cleanup/ explains turn raw card descriptors into clean merchant display names.
- /solutions/card-transaction-descriptor-parser/ explains parse processor wrappers, locations, and noisy fragments from card rows.
- /solutions/transaction-categorization-api/ explains return usable categories with merchant confidence and warnings.
- /solutions/mcc-code-cleanup/ explains combine MCC context with merchant cleanup instead of treating MCC as identity.
- /solutions/transaction-confidence-scoring/ explains show confidence bands for merchant cleanup decisions.
- /solutions/low-confidence-transaction-warnings/ explains return warnings instead of fake certainty for ambiguous transactions.
- /solutions/merchant-logo-metadata-api/ explains return reviewed logo variant metadata for transaction UIs.
- /solutions/merchant-website-matching/ explains attach website fields only when identity evidence is strong.
- /solutions/recurring-transaction-detection/ explains surface recurrence hints for subscription-like rows.
- /solutions/subscription-merchant-detection/ explains identify subscription merchants without uploading statements.
- /solutions/processor-descriptor-cleanup/ explains normalize Square, Stripe, PayPal, Shopify, and other wrapper text.
- /solutions/square-transaction-descriptor-cleanup/ explains clean SQ-prefixed merchant descriptors.
- /solutions/stripe-transaction-descriptor-cleanup/ explains clean Stripe-style card statement text for product display.
- /solutions/paypal-transaction-descriptor-cleanup/ explains clean PayPal-wrapped merchant rows.
- /solutions/shopify-transaction-descriptor-cleanup/ explains clean Shopify storefront descriptors for transaction UI.
- /solutions/expense-transaction-cleanup/ explains make team expense rows readable before review workflows.
- /solutions/budgeting-app-transaction-cleanup/ explains make personal finance feeds readable and confidence-aware.
- /solutions/accounting-transaction-import-cleanup/ explains clean imported transaction display labels before categorization review.
- /solutions/cashback-transaction-feed-matching/ explains improve merchant display and confidence for cashback feed rows.
- /solutions/loyalty-transaction-feed-cleanup/ explains clean loyalty-program transaction feeds without overclaiming merchant identity.
- /solutions/receipt-matching-merchant-cleanup/ explains make merchant labels cleaner before receipt matching workflows.
- /solutions/enrich-transactions-without-pii/ explains enrich one safe descriptor without card numbers, account numbers, or full statements.
- /solutions/deterministic-transaction-enrichment/ explains avoid unpredictable live research during transaction display rendering.
- /solutions/transaction-enrichment-without-llm-request-path/ explains keep transaction enrichment fast and repeatable without live prompts.

## Integration Cleanup Routes

- /integrations/plaid-transaction-cleanup/ explains clean merchant display after Plaid transaction ingestion.
- /integrations/yodlee-transaction-cleanup/ explains clean Yodlee-fed transaction rows for product UI.
- /integrations/mx-transaction-cleanup/ explains clean MX-backed transaction rows for display.
- /integrations/teller-transaction-enrichment/ explains enrich Teller-backed transaction descriptors for UI display.
- /integrations/finicity-transaction-cleanup/ explains clean Finicity-fed transaction rows after aggregation.
- /integrations/akoya-transaction-cleanup/ explains clean Akoya-fed transaction descriptors for product display.
- /integrations/tink-transaction-cleanup/ explains clean Tink-fed transaction rows without live vendor calls.
- /integrations/truelayer-transaction-cleanup/ explains clean TrueLayer-backed transaction rows for app display.

## Technology Library Routes

- /libraries/transaction-enrichment-library-javascript/ explains JavaScript developers searching for a transaction enrichment library that can call a simple API.
- /libraries/transaction-enrichment-library-typescript/ explains TypeScript teams looking for typed transaction enrichment API usage without inventing merchant cleanup logic.
- /libraries/transaction-enrichment-library-node-js/ explains Node.js developers adding transaction enrichment to a backend service.
- /libraries/transaction-enrichment-library-express/ explains Express applications that need a backend transaction enrichment route.
- /libraries/transaction-enrichment-library-nestjs/ explains NestJS services adding merchant cleanup through a small enrichment service.
- /libraries/transaction-enrichment-library-python/ explains Python developers searching for transaction enrichment API examples.
- /libraries/transaction-enrichment-library-fastapi/ explains FastAPI apps adding a safe one-descriptor enrichment endpoint.
- /libraries/transaction-enrichment-library-django/ explains Django applications enriching transaction rows before display.
- /libraries/transaction-enrichment-library-flask/ explains Flask apps adding a lightweight transaction enrichment endpoint.
- /libraries/transaction-enrichment-library-ruby/ explains Ruby developers calling a transaction enrichment API from server-side code.
- /libraries/transaction-enrichment-library-rails/ explains Rails applications that need cleaner merchant names and warnings for transaction UI.
- /libraries/transaction-enrichment-library-php/ explains PHP developers adding transaction enrichment through a direct API request.
- /libraries/transaction-enrichment-library-laravel/ explains Laravel applications enriching transaction descriptors through a backend HTTP client.
- /libraries/transaction-enrichment-library-java/ explains Java services that need merchant cleanup through an HTTP enrichment API.
- /libraries/transaction-enrichment-library-spring-boot/ explains Spring Boot teams adding transaction enrichment to a backend service.
- /libraries/transaction-enrichment-library-kotlin/ explains Kotlin services calling a transaction enrichment API for merchant display metadata.
- /libraries/transaction-enrichment-library-go/ explains Go backend services enriching transaction descriptors with a bounded HTTP call.
- /libraries/transaction-enrichment-library-rust/ explains Rust services integrating transaction enrichment through an explicit HTTP client.
- /libraries/transaction-enrichment-library-dotnet/ explains .NET teams adding transaction enrichment to server-side finance applications.
- /libraries/transaction-enrichment-library-c-sharp/ explains C# developers adding merchant cleanup with HttpClient and the TxnKit API.
- /libraries/transaction-enrichment-library-swift/ explains Swift developers using a server-owned API key or trusted backend to enrich transaction display rows.
- /libraries/transaction-enrichment-library-ios/ explains iOS apps that need transaction enrichment through a backend or carefully controlled service boundary.
- /libraries/transaction-enrichment-library-android-kotlin/ explains Android apps displaying cleaner merchant rows through a transaction enrichment API boundary.
- /libraries/transaction-enrichment-library-react/ explains React applications that need transaction enrichment through a backend proxy.
- /libraries/transaction-enrichment-library-next-js/ explains Next.js applications adding a server route for transaction enrichment.
- /libraries/transaction-enrichment-library-vue/ explains Vue applications calling a backend transaction enrichment endpoint.
- /libraries/transaction-enrichment-library-nuxt/ explains Nuxt applications adding a server API route for transaction enrichment.
- /libraries/transaction-enrichment-library-sveltekit/ explains SvelteKit apps adding a server endpoint for merchant cleanup.
- /libraries/transaction-enrichment-library-angular/ explains Angular applications that need transaction enrichment through a backend API boundary.
- /libraries/transaction-enrichment-library-cloudflare-workers/ explains Cloudflare Workers routes that proxy safe descriptor enrichment with server-side secrets.
<!-- SEO_LANDING_ROUTES_END -->