API Reference

Browse and test Width AML API endpoints

Base URLhttps://api.trustin.bond

For agentsllms-full.txtllms.txtopenapi.jsonSKILL.mdMCP https://api.trustin.bond/mcp

Hand an agent llms-full.txt, or the MCP endpoint with your API key, and it can screen and manage rules without reading this page.

GEThttps://api.trustin.bond/api/v3/chains

Supported Chains (v3)

The chains and canonical assets screening accepts, read live from the investigation backend — a value returned here is one screen/kya and screen/kyt will take. Use it to render a chain selector or validate input instead of hardcoding a list that goes stale when a chain is added. address_family says which address form a chain uses ("evm" or "tron"): a 0x… address is shared by every EVM chain, so resolving a bare address to a chain needs it. default_token is what the screening endpoints use when a request omits token. Auth: API key, same as the other v3 endpoints; nothing is charged — this is metadata, not a screening. GET and POST both work.

Request Parameters

Request Code
curl 'https://api.trustin.bond/api/v3/chains?apikey=YOUR_API_KEY'

Run the request to see the response here.

Response Fields
chains[].chain_namestring

Value to send as chain_name on the screening endpoints

chains[].tokensarray

Canonical assets screenable on this chain

chains[].default_tokenstring

Asset used when a screening request omits token

chains[].address_familystring

Address form this chain uses: evm (0x… hex) or tron (base58)

Example Response

Response
{
"code": 0,
"msg": "success",
"data": {
"chains": [
{
"chain_name": "Ethereum",
"tokens": [
"usdc",
"usdt"
]
,
"default_token": "usdt",
"address_family": "evm"
}
,
{
"chain_name": "Tron",
"tokens": [
"usdt"
]
,
"default_token": "usdt",
"address_family": "tron"
}
,
{
"chain_name": "Base",
"tokens": [
"usdc"
]
,
"default_token": "usdc",
"address_family": "evm"
}
]
}
}