Notabene

Name: Notabene API
Brand: Notabene
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity Verificationbearer115 EndpointsREST

For Agents

Run crypto compliance workflows: Travel Rule transactions, sanctions screening, address ownership checks, and counterparty risk via Chainalysis, TRM, and LexisNexis integrations.

Connect the Notabene to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Notabene, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 Notabene API.

Submit and track Travel Rule transactions between VASPs with originator and beneficiary data

Screen counterparty addresses against Chainalysis, TRM, and Coinfirm risk feeds

Run KYC and sanctions checks on individuals via the LexisNexis integration

GET STARTED

Start building with Notabene API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Notabene, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Notabene API for, with concrete tasks.

★ 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.

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.

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.

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.

For a pending Travel Rule transaction, fetch counterparty VASP details, address ownership, and Chainalysis risk, then summarise a release recommendation

Key Endpoints

115 endpoints — jentic publishes the only available openapi specification for notabene, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/address/registerCustomer

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

POST

/address/registerCustomer

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Notabene bearer JWTs and VASP credentials are stored in the Jentic vault. Agents request execution and Jentic injects the JWT at call time — raw tokens never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'screen a wallet address') and Jentic returns the right Notabene operation across the Chainalysis, TRM, or address-book endpoints with its input schema attached.

Time to first call

Direct Notabene integration: 1-2 weeks for auth, Travel Rule message handling, and per-provider screening flows. Through Jentic: under a day — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sumsub API

Sumsub focuses on KYC and identity verification but does not provide Travel Rule messaging between VASPs.

Choose Sumsub when you need document-based KYC and biometrics; choose Notabene when the workflow involves Travel Rule or counterparty VASP discovery.

Complementary

CoinAPI

CoinAPI provides crypto market data; pair with Notabene to value transactions screened for compliance.

Use CoinAPI to convert on-chain amounts to fiat for reporting, and Notabene to handle the compliance side of the same transaction.

Complementary

Covalent (GoldRush) API

Covalent provides on-chain data; combine with Notabene's risk screening for richer transaction context.

Use Covalent when you need raw on-chain history for an address; use Notabene when you need attributed risk and Travel Rule messaging.

FAQs

Specific to using Notabene API through Jentic.

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 at https://app.jentic.com/sign-up.

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.