x402 census · api.ibanforge.com · 8039140fa5cb · JSON
POST /v1/iban/validate
live
Validate a European IBAN and enrich it with bank, compliance and routing data. Use whenever the user mentions an IBAN, a bank account, a SEPA payment or asks who the bank is. Returns: valid, country, BIC/SWIFT, bank name, EMI/vIBAN flag, SEPA + VoP reachability, risk score, Swiss bc_nummer for CH/LI. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping)…
Verdict: live. The unpaid GET reached a valid 402 (confirmed by the re-probe of 2026-10-01).
Facts from the catalogs
| Field | Value |
|---|---|
| URL | https://api.ibanforge.com/v1/iban/validate |
| Method | POST |
| Price | $0.005 USDC = 5000 atomic units of 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Network | eip155:8453 (base) |
| payTo | 0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55 |
| Seller | api.ibanforge.com |
| Catalogs | cdp (row updated 2026-09-06) |
| Listed since (lower bound) | 2026-09-06 (earliest catalog timestamp; catalogs report last-update times only) |
| Last catalog update | 2026-09-06 |
| CDP quality counters | 2 calls and 1 unique payers in 30 days, last call 2026-09-06 (catalog-reported, not verified on chain) |
| Category (keyword rule) | enrichment/people |
| Templated path | no |
| x402Version in catalog | 2 |
| Service name / tags | IBANforge · iban, bic, sepa, compliance, banking |
Unpaid probe (census of )
| Field | Value |
|---|---|
| Probe | not probed in this build |
Latest re-probe
| Field | Value |
|---|---|
| Re-probed at | 2026-10-01T03:13:24.000Z (cron) |
| Verdict now | live changed from unprobed |
| HEAD / GET | 402 / 402 |
| accepts[0] | {"scheme":"exact","network":"eip155:8453","amount":"5000","payTo":"0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","maxTimeoutSeconds":60,"extra":{"name":"USD Coin","version":"2"}} |
| Live amount equals catalog price | yes |
| Latency | 2,655 ms |
| Error | none |
On-chain facts for the payTo (public address)
| Field | Value |
|---|---|
| Settlement history | unresolved: payTo not seen in the payer forensics (180 wallets' outbound history) or the Blockscout sample |
Declared input and output (extensions.bazaar)
{
"input": {
"body": {
"iban": "CH1000230000000012345"
},
"bodyType": "json",
"discoverable": true,
"method": "POST",
"schema": {
"properties": {
"iban": {
"description": "IBAN to validate (spaces and lowercase accepted).",
"maxLength": 34,
"minLength": 15,
"type": "string"
}
},
"required": [
"iban"
],
"type": "object"
},
"type": "http"
},
"output": {
"type": "json",
"example_truncated": true,
"chars": 1213
}
}
Try it (unpaid: shows the 402)
curl -si -X POST 'https://api.ibanforge.com/v1/iban/validate' -H 'accept: application/json' -H 'content-type: application/json' --data '{}'
The catalog declares POST. A 402 answer carries the payment requirements in the JSON body and, for x402 v2, base64 in the PAYMENT-REQUIRED header. This page never sends a payment.
Paid checks (x402, USDC on Base)
GET https://bazaar.agentexchange.work/r/8039140fa5cb/probe.json re-runs this probe right now for $0.01 and writes the result here. POST https://bazaar.agentexchange.work/featured with {"id":"8039140fa5cb"} places this resource at the top of the report and search pages for 30 days for $1.00, labelled. Unpaid requests answer 402 with the terms. Pricing.
Catalog references: agentic.market (CDP Bazaar front end) · this record as JSON · all resources on api.ibanforge.com.