Validate a US ABA routing number API

Validate a 9-digit US ABA routing number checksum (weights 3-7-1). Bank directory names are not returned in this version.

The Validate a US ABA routing number operation is part of the Open Banking & Payment Intelligence API on BRAINIAC.software. Validate a 9-digit US ABA routing number checksum (weights 3-7-1). Bank directory names are not returned in this version. It is exposed as POST /api/v1/payment-intelligence/routing-number-validate and priced at $0.02 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied transactions Optional merchant directory Optional category corrections Public IBAN Registry lengths and ABA checksum rules Limitations: No bank account is connected and no Open Banking credentials are used. Income and affordability figures use only labeled supplied rows. Recurring detection uses date spacing and merchant/amount similarity in the request set. An affordability or credit decision is never produced. Missing merchants, categories, and amounts are not invented. IBAN/ABA checks validate structure and checksum only; live bank-directory names are not returned in this version. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Classify open-banking transactions, Detect recurring payments, Identify subscription spend, Resolve merchant identity. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.02 USDC
/api/v1/payment-intelligence/routing-number-validate

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/payment-intelligence/routing-number-validate" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "routingNumber": "021000021"
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Open Banking & Payment Intelligence APIFull docsHow it works