canonical: https://jentic.com/apis/notabene.id/notabene # Notabene Id Notabene Jentic publishes the only available OpenAPI specification for Notabene, keeping it validated and agent-ready. Notabene is a crypto compliance platform that helps Virtual Asset Service Providers (VASPs) implement the FATF Travel Rule, sanctions screening, and counterparty due diligence. The API exposes 115 endpoints covering travel rule transactions, address ownership and screening, customer KYC, document handling, and integrations with Chainalysis, TRM, Coinfirm, LexisNexis, and BitGo. It supports the operational compliance flow that lets a VASP transact safely with other VASPs and self-hosted wallets. ## For AI agents Run crypto compliance workflows: Travel Rule transactions, sanctions screening, address ownership checks, and counterparty risk via Chainalysis, TRM, and LexisNexis integrations. ## Scope Does not handle on-chain settlement, custody, or fiat banking - use for crypto compliance, Travel Rule messaging, and counterparty screening only. ## Capabilities - Submit and track Travel Rule transactions between VASPs with originator and beneficiary data - Register customer wallet addresses and look up address ownership across the Notabene network - Screen counterparty addresses against Chainalysis, TRM, and Coinfirm risk feeds - Run KYC and sanctions checks on individuals via the LexisNexis integration - Manage VASP user accounts, API credentials, and permission scopes - Upload and exchange compliance documents tied to a transaction or counterparty ## Use cases ### Travel Rule Compliance for Crypto Exchanges A VASP must collect originator and beneficiary information for crypto transfers above the FATF threshold and exchange that data with the counterparty VASP before settlement. Notabene handles the messaging, counterparty discovery, and acknowledgement workflow so the exchange can prove compliant transmission. Endpoints under `/v1/transactions` and /address cover the full submit-and-confirm cycle. Example prompt: Submit a Travel Rule transaction with originator name, beneficiary VASP DID, and 0.5 BTC amount, then poll for counterparty acknowledgement ### Counterparty Address Risk Screening Before a deposit or withdrawal settles, a compliance system screens the counterparty address against blockchain analytics providers and the address-ownership graph. Notabene unifies Chainalysis, TRM, and Coinfirm feeds behind a single API, returning ownership attribution and risk scores so a transaction can be cleared or held for review. Example prompt: Look up address ownership for a destination Bitcoin address and pull a Chainalysis risk score, then return a clear or hold decision ### KYC and Sanctions Screening When onboarding a customer, a VASP needs to run sanctions and PEP checks against authoritative lists. The Notabene LexisNexis and TRMSanctions endpoints take a customer profile and return screening results that the VASP can persist alongside the customer record. This replaces a direct LexisNexis integration with a single Notabene call. Example prompt: Run a LexisNexis sanctions screen on a new customer with name, date of birth, and country of residence, and persist the result ### AI Agent Compliance Triage A compliance agent in a VASP back-office reviews queued Travel Rule messages and address screening results to recommend hold or release. Through Jentic, the agent searches for the right Notabene operation, loads the schema, and pulls the supporting evidence - counterparty status, Chainalysis score, address ownership - into a single decision pack. Example prompt: For a pending Travel Rule transaction, fetch counterparty VASP details, address ownership, and Chainalysis risk, then summarise a release recommendation ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/address/registerCustomer` | Register a customer wallet address | | GET | `/v1/addresses/address-ownerships/{address}` | Look up address ownership | | POST | `/auth/customerToken` | Issue a customer access token | | GET | `/auth/credentials/{vaspDID}` | List VASP API credentials | | POST | `/auth/credentials/{vaspDID}` | Create VASP API credentials | | GET | `/auth/vaspUsers/{vaspDID}` | List VASP users | ## Key resources - **Transactions** — Submit and track Travel Rule transactions between VASPs - **Address Book** — Register and look up customer and counterparty wallet addresses - **TrustFramework** — Counterparty VASP discovery and trust scoring - **Chainalysis** — Address risk screening via Chainalysis - **TRM / TRMSanctions** — TRM Labs risk and sanctions screening - **Coinfirm** — Coinfirm AML risk feeds - **LexisNexis** — Customer KYC and sanctions screening - **Documents** — Upload and exchange compliance documents - **Auth / Credentials** — Manage VASP users, API credentials, and access tokens ## Why Jentic - **Setup:** Wiring Notabene by hand means managing its bearer JWTs and VASP credentials against api.notabene.id and threading them through Travel Rule and screening calls yourself across more than a hundred endpoints. Through Jentic you install once, import Notabene from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Notabene puts the VASP DID in the URL path (`/auth/credentials/{vaspDID}`), so a rule can pin your agent to one VASP for credential reads. You choose the operations it may call, so writing credentials or registering a customer is not included unless you add it. - **Credential handling:** Your Notabene bearer JWT and VASP credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'screen a wallet address' or 'check address ownership', and Jentic returns the matching Notabene operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Sumsub API** — Sumsub focuses on KYC and identity verification but does not provide Travel Rule messaging between VASPs. - **CoinAPI** — CoinAPI provides crypto market data; pair with Notabene to value transactions screened for compliance. - **Covalent (GoldRush) API** — Covalent provides on-chain data; combine with Notabene's risk screening for richer transaction context. ## FAQ ### Why is there no official OpenAPI spec for Notabene? Notabene does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Notabene via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Notabene API use? Notabene uses HTTP bearer authentication with JWT tokens. Customer-scoped tokens are obtained via `/auth/customerToken.` Through Jentic, tokens are held in the vault and injected at execution time so the agent never handles the raw JWT. ### Can I screen addresses against multiple risk providers with the Notabene API? Yes. Notabene exposes dedicated endpoints for Chainalysis, TRM (including TRMSanctions), and Coinfirm under separate path groups, so a single integration can pull risk data from all three without writing direct vendor integrations. ### What are the rate limits for the Notabene API? The OpenAPI spec does not declare specific rate limits. Notabene applies tenant-level limits in production; consult the Notabene developer portal for current values and back off on 429 responses. ### How do I submit a Travel Rule transaction through Jentic? Search Jentic for 'submit a travel rule transaction'. Jentic returns the matching Notabene transaction submission operation along with its input schema covering originator, beneficiary, and counterparty VASP DID, so the agent can call it directly without browsing the Notabene docs. ### Can I run KYC checks on customers through this API? Yes. The LexisNexis path group provides KYC, sanctions, and PEP screening on customer profiles, and TRMSanctions covers blockchain-address sanctions hits. Persist the screening result against the customer record in your own system. ### Can I limit what my agent is allowed to do with the Notabene API? Yes. Because Jentic One is self-hosted, your own rules decide which Notabene operations and credentials the agent may use. Notabene puts the VASP DID in the URL path, such as `/auth/credentials/{vaspDID}`, so you can pin the agent to a single VASP for credential reads. You choose the operations it may call, so writing credentials or registering a customer address stays off-limits unless you explicitly grant it.