Enroll your BitGo-managed VASP in the Notabene network: obtain a Notabene API key and VASP DID via the Notabene dashboard at app.notabene.id
Before initiating an outbound transfer, call the Notabene VASP discovery endpoint (GET https://api.notabene.id/tf/simple/vasps?address=<destination_address>) to determine if the destination address belongs to a regulated VASP
If a beneficiary VASP is identified, call Notabene txCreate (POST https://api.notabene.id/tf/transaction) with IVMS101-formatted originator and beneficiary data plus the transaction amount and asset
Monitor the travel rule transaction status via GET https://api.notabene.id/tf/transaction/{transactionId}; wait for status ACK_ACCEPTED or the applicable jurisdiction's required confirmation before broadcasting the BitGo transfer
On REJECTED or UNVERIFIED status, hold the BitGo transfer and flag for compliance review — do not broadcast to chain until Travel Rule clearance is obtained
Log the Notabene transactionId alongside the BitGo transferId and on-chain txHash in your compliance records for audit trail
Known gotchas
Notabene PII data must be encrypted using the beneficiary VASP's public key via the Notabene PII SDK before sending — sending plaintext PII to the API returns a validation error and constitutes a data handling violation
The TRUST network (operated by Coinbase) and the Notabene network are separate directories; a VASP reachable on TRUST may not be in the Notabene directory and vice versa — implement fallback discovery logic
Travel Rule message exchange must precede on-chain broadcasting in FATF-aligned jurisdictions; post-hoc Travel Rule filing is generally non-compliant and may result in regulatory action
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp