Issuer Check

{
  "answer": {
    "controls": {
      "allow_trustline_clawback": true,
      "blackholed": false,
      "default_ripple": true,
      "global_freeze": false,
      "has_multisign": true,
      "has_regular_key": false,
      "master_key_disabled": true,
      "no_freeze": false,
      "require_auth": false,
      "require_destination_tag": true
    },
    "domain": {
      "account_listed_in_toml": true,
      "claimed_domain": "ripple.com",
      "raw_domain_field": "https://ripple.com/",
      "toml_organization": "Ripple XRP Ledger Operations Team",
      "toml_url": "https://ripple.com/.well-known/xrp-ledger.toml"
    },
    "issued_tokens": [
      {
        "currency": "RLUSD",
        "currency_code": "524C555344000000000000000000000000000000",
        "outstanding": "1029443742.861488"
      }
    ],
    "summary": "The account names this domain on-ledger, and the domain lists this account back. Both sides agree.",
    "verdict": "domain_verified",
    "xrp_balance": "99.77836"
  },
  "checked_at": "2026-10-18T03:48:43+00:00",
  "proof": {
    "account": "rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De",
    "ledger_index": 107731437,
    "network": "xrpl:0 (mainnet)",
    "sources": [
      {
        "method": "account_info, gateway_balances",
        "name": "XRP Ledger public server",
        "url": "https://s1.ripple.com:51234/"
      },
      {
        "method": "two-way domain check",
        "name": "ripple.com xrp-ledger.toml",
        "url": "https://ripple.com/.well-known/xrp-ledger.toml"
      }
    ],
    "validated": true
  },
  "service": "issuer_check",
  "unknowns": [
    "Legal identity and solvency of the issuer (the ledger and toml file cannot prove these).",
    "Whether the domain owner is trustworthy; a verified domain only proves both sides point at each other."
  ]
}

# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://bruk-agent-api.fly.dev/v1/issuer-check?account=rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://bruk-agent-api.fly.dev/v1/issuer-check?account=rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode

// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fbruk-agent-api.fly.dev%2Fv1%2Fissuer-check
const res = await pay("https://bruk-agent-api.fly.dev/v1/issuer-check?account=rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De");
console.log(res.status, await res.text());

# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://bruk-agent-api.fly.dev/v1/issuer-check?account=rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De")
    print(res.status_code, res.text)