Breadcrumbs One
✓ Official Vendor SpecSecurityComplianceapiKey5 EndpointsREST
For Agents
Score blockchain addresses and transactions for AML risk, look up address attribution, and check sanctions lists through the Breadcrumbs One compliance API.
Use for: I want to score a bitcoin address for AML risk, Check whether a wallet address is on a sanctions list, Retrieve the entity attribution for a blockchain address, Get the risk score for a specific transaction hash
Not supported: Does not handle KYC document verification, identity matching, or transaction execution — use for blockchain address risk scoring, attribution, and sanctions screening only.
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.
Install Jentic One Beta
Connect the Breadcrumbs One to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Breadcrumbs One, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Breadcrumbs One API.
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
Patterns agents use Breadcrumbs One API for, with concrete tasks.
★ 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.
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.
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.
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.
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
5 endpoints — 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.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Breadcrumbs X-API-KEY header is stored encrypted in the Jentic vault and attached to outgoing requests at execution time. Compliance teams keep one key per environment; agents call /risk/address, /sanctioned_address, and /attribution by intent without ever seeing the raw key.
Intent-based discovery
Agents search Jentic for intents like 'screen a crypto address for AML risk' or 'check if an address is sanctioned' and Jentic returns the matching Breadcrumbs operation (GET /risk/address, POST /sanctioned_address) with input parameters typed.
Time to first call
Direct Breadcrumbs integration: a day or two to wire the API key, retry logic, and response parsing across the five endpoints. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Breadcrumbs One API through Jentic.
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.
GET STARTED