api.ibanforge.com
Developer tools API on Base, paid per request with x402.
- Endpoints4
- Price per requestfrom $0.002
- Outside payers · 7dn/a
- Answer 4021 of 1
Overview
- Seller wallet
- 0xd13bd0a4120ba301125290e5cc0c7efd4cb40a55
- Chains
- Base
- Hosts
- api.ibanforge.com
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Developer tools3Security1
- First seen
- 2026-10-05 · last seen 2026-11-20
Endpoints
EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.https://api.ibanforge.com/v1/iban/batch
Validate up to 100 IBANs in one call at $0.002 per IBAN (2.5x cheaper per IBAN than single calls at $0.005, and one settlement instead of N). A quote asked for without a body is the 1-IBAN minimum, $0.002 — the same fig…
BaseDeveloper tools$0.002/ request
2026-11-20
https://api.ibanforge.com/v1/bic/:code
Resolve a BIC/SWIFT code (8 or 11 chars) into the underlying bank: name, country, city, LEI, and registered head-office address (where available). Use only when you already have the BIC — for IBAN inputs, prefer /v1/iba…
BaseDeveloper tools$0.003/ request
2026-11-15
https://api.ibanforge.com/v1/iban/validate
Validate an IBAN (89 countries) with bank and routing data. Use whenever an IBAN or a bank account comes up. Returns: valid, country, bank-code verdict (national register in DE, AT, BE, SK, CZ, BG, CH, LI), BIC and bank…
BaseDeveloper tools$0.005/ request
2026-11-20
https://api.ibanforge.com/v1/iban/compliance
Pre-payment triage of the bank behind an IBAN: OFAC, EU and UN lists matched on the bank (BIC8), the country against a fixed sanctions list, never the payee's name; FATF status; SEPA Instant reachability; whether the EP…
BaseSecurity$0.02/ request
2026-11-20
Evidence
Answers HTTP 402
Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.1 of 1
1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload
checked 2026-09-28
x402-style payments, 7-day window (Base)
x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.unknown
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read))
window ended 2026-11-19
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0xd13bd0a4120ba301125290e5cc0c7efd4cb40a55 | 4 | 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload 2026-09-28 | unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)) |
One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.
Pricing
The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.
Claim this merchant
Sign a message from the payout address 0xd13bd0…b40a55 to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.
Data CC-BY-4.0, attribution: data by satohub.ai. Data: x402-list.com (CC BY 4.0). Data as of 2026-11-20. Appearing here is not an endorsement. Check an endpoint with the doctor.