canonical: https://jentic.com/apis/breadcrumbs.one/breadcrumbs # Breadcrumbs One Breadcrumbs One is a blockchain analytics and AML compliance API that lets fintech, crypto, and compliance teams assess risk on blockchain addresses and transactions before processing or accepting them. Five endpoints cover attribution lookups, transaction graph traversal for incoming and outgoing flows, per-address and per-transaction risk scoring, and sanctioned-address screening against Breadcrumbs' watchlists. Authentication is a single X-API-KEY header. The API suits exchanges, custody platforms, and payment processors that need to make a real-time accept/reject decision on a wallet address or transaction. ## For AI agents Score blockchain addresses and transactions for AML risk, look up address attribution, and check sanctions lists through the Breadcrumbs One compliance API. ## Scope Does not handle KYC document verification, identity matching, or transaction execution - use for blockchain address risk scoring, attribution, and sanctions screening only. ## Capabilities - Get a risk score for a single blockchain address via GET /risk/address - Score every address involved in a transaction via GET /risk/transaction - Resolve attribution (entity, exchange, mixer, etc.) for an address via POST /attribution - Inspect incoming and outgoing transactions for an address via POST /node for graph analysis - Screen one or more addresses against Breadcrumbs' sanctions lists via POST /sanctioned_address ## Use cases ### Crypto exchange withdrawal screening Before releasing a withdrawal to an external address, run it through Breadcrumbs to confirm it is not sanctioned and does not exceed the platform's risk threshold. The flow calls POST /sanctioned_address with the destination, then GET /risk/address for a numeric score, and only releases the funds if both checks pass. This automates a key control AML teams previously ran by hand. Example prompt: POST /sanctioned_address with the destination address; if not sanctioned, GET /risk/address with the same address and reject the withdrawal if the risk score exceeds 70. ### Inbound deposit attribution and risk When a user funds an account with crypto, identify which entity the deposit came from (a major exchange, a mixer, a darknet market) and decide how to treat it. POST /attribution returns the attributed entity if known; GET /risk/transaction scores every input address in the transaction so the deposit can be auto-credited, held for review, or rejected. Example prompt: On deposit, POST /attribution with the source address; if attribution returns a flagged entity, GET /risk/transaction with the txid and hold the deposit if any input scores above the policy threshold. ### Transaction graph investigation Compliance analysts trace funds backwards or forwards from a suspect address to map exposure to mixers, sanctioned entities, or peer wallets. POST /node returns incoming and outgoing transactions for an address, providing the edges needed to expand the graph one hop at a time. This replaces manual block-explorer scraping during STR/SAR investigations. Example prompt: POST /node with the suspect address, then for each connected counterparty above a value threshold, POST /attribution and GET /risk/address to expand the investigation graph. ### AI agent integration via Jentic An agent reviewing a payout queue can discover Breadcrumbs through Jentic, load the risk and sanctions operations, and execute them without ever holding the X-API-KEY in its prompt context. Jentic injects the key at execution time and returns typed risk scores and sanctions-match flags the agent can act on. Example prompt: Through Jentic, search 'screen a crypto address for AML risk', load the GET /risk/address operation, and execute with the address from the payout queue. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /risk/address | Risk score for a single blockchain address | | GET | /risk/transaction | Risk scores for every address in a transaction | | POST | /attribution | Entity attribution for an address | | POST | /node | Incoming and outgoing transactions for an address | | POST | /sanctioned_address | Sanctions list screening for one or more addresses | ## Key resources - **Risk scoring** — Per-address and per-transaction risk scores via /risk/address and /risk/transaction - **Attribution** — Entity attribution lookups for addresses via /attribution - **Transaction graph** — Incoming and outgoing transactions for an address via /node - **Sanctions screening** — Sanctioned-address checks via /sanctioned_address ## Why Jentic - **Setup:** Wiring Breadcrumbs by hand means setting the X-API-KEY header, managing one key per environment, and coordinating the risk, attribution, and sanctions calls yourself. Through Jentic you install once, import the Breadcrumbs One API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Breadcrumbs takes the address or transaction in the query string or request body rather than a resource path, so scope the agent to the operations it needs, such as scoring an address risk or screening for sanctions, and add attribution or node writes only if the agent requires them. Every operation you allow is one you have explicitly chosen. - **Credential handling:** Your Breadcrumbs X-API-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 'screen a crypto address for AML risk' or 'check if an address is sanctioned', and Jentic returns the matching Breadcrumbs operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **BraveNewCoin API** — Use BraveNewCoin for crypto market data alongside Breadcrumbs' AML risk scoring - **Braintree GraphQL API** — Run Breadcrumbs sanctions checks before reconciling fiat payouts originating from crypto on-ramps - **Braze Endpoints** — Trigger Braze customer messages when a Breadcrumbs check forces a withdrawal hold ## FAQ ### What authentication does the Breadcrumbs One API use? Every request must include an X-API-KEY header with the customer's API key issued in the Breadcrumbs dashboard. Through Jentic, the key is held in the encrypted vault and attached to outgoing requests at execution time, so the agent never holds it in prompt context. ### Can I screen an address against sanctions lists with the Breadcrumbs One API? Yes. POST /sanctioned_address accepts an array of addresses and returns which (if any) appear on Breadcrumbs' sanctioned lists. Run it as a hard gate before releasing crypto withdrawals or accepting deposits from external counterparties. ### How do I get a risk score for a blockchain transaction? Call GET /risk/transaction with the transaction id (txid). The response scores every input and output address so the worst-case score can be used as the transaction's overall risk. For a single wallet, use GET /risk/address instead. ### What are the rate limits for the Breadcrumbs One API? The OpenAPI spec does not enumerate rate limits - quotas depend on the Breadcrumbs plan. For batch screening jobs that fan out POST /sanctioned_address or GET /risk/address calls, throttle client-side and back off on 429 responses. ### How do I check a crypto withdrawal address with the Breadcrumbs One API through Jentic? Install with pip install jentic, then await client.search('screen a crypto address for AML risk'), await client.load on the GET /risk/address operation, and await client.execute with the address. Jentic attaches the X-API-KEY header automatically. ### Does the Breadcrumbs One API attribute addresses to entities? Yes. POST /attribution returns the attributed entity for an address when Breadcrumbs has it indexed (for example a major exchange, a known mixer, or a darknet market). Use it together with risk scoring to decide whether to credit, hold, or reject inbound funds. ### Can I limit what my agent is allowed to do with the Breadcrumbs One API? Yes. Because you run Jentic One yourself, your own rules decide which Breadcrumbs operations and credentials the agent can use. Breadcrumbs takes the address or transaction in the query string or request body rather than a resource path, so you scope the agent to only the operations it needs, such as GET /risk/address or POST /sanctioned_address, and you can withhold POST /attribution or POST /node if the agent does not need them. Every operation you allow is one you have explicitly chosen.