api.ibanforge.com

https://api.ibanforge.com/v1/bic/:code

Shares a payout wallet with 4 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

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/iban/validate which resolves the BIC for you. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) · 121,000+ BICs (39,000+ LEI-enriched via GLEIF, refreshed monthly) · v1.4.4.

57
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Tue 12 AMThu 5 AMSat 10 AMMon 10 PM

Response time

p50 446ms · p95 482ms
0ms 550ms 1100ms Tue 12 AMThu 5 AMSat 10 AMMon 10 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/29/2026, 12:00:00 AM 100% 1 456ms
9/29/2026, 1:00:00 AM 100% 1 466ms
9/29/2026, 3:00:00 AM 100% 1 448ms
9/29/2026, 5:00:00 AM 100% 1 463ms
9/29/2026, 7:00:00 AM 100% 1 459ms
9/29/2026, 9:00:00 AM 100% 1 461ms
9/29/2026, 11:00:00 AM 100% 1 442ms
9/29/2026, 1:00:00 PM 100% 1 159ms
9/29/2026, 2:00:00 PM 100% 1 469ms
9/29/2026, 4:00:00 PM 100% 1 436ms
9/29/2026, 7:00:00 PM 100% 1 480ms
9/29/2026, 9:00:00 PM 100% 1 456ms
9/29/2026, 11:00:00 PM 100% 1 459ms
9/30/2026, 1:00:00 AM 100% 1 465ms
9/30/2026, 3:00:00 AM 100% 1 471ms
9/30/2026, 5:00:00 AM 100% 1 430ms
9/30/2026, 7:00:00 AM 100% 1 447ms
9/30/2026, 9:00:00 AM 100% 1 443ms
9/30/2026, 11:00:00 AM 100% 1 448ms
9/30/2026, 1:00:00 PM 100% 1 483ms
9/30/2026, 3:00:00 PM 100% 1 457ms
9/30/2026, 5:00:00 PM 100% 1 425ms
9/30/2026, 7:00:00 PM 100% 1 461ms
9/30/2026, 9:00:00 PM 100% 1 449ms
9/30/2026, 11:00:00 PM 100% 1 436ms
10/1/2026, 1:00:00 AM 100% 1 475ms
10/1/2026, 3:00:00 AM 100% 1 443ms
10/1/2026, 5:00:00 AM 100% 1 443ms
10/1/2026, 7:00:00 AM 100% 1 452ms
10/1/2026, 9:00:00 AM 100% 1 434ms
10/1/2026, 11:00:00 AM 100% 1 458ms
10/1/2026, 1:00:00 PM 100% 1 440ms
10/1/2026, 3:00:00 PM 100% 1 465ms
10/1/2026, 5:00:00 PM 100% 1 1081ms
10/1/2026, 7:00:00 PM 100% 1 461ms
10/1/2026, 9:00:00 PM 100% 1 461ms
10/1/2026, 11:00:00 PM 100% 1 504ms
10/2/2026, 1:00:00 AM 100% 1 437ms
10/2/2026, 3:00:00 AM 100% 1 469ms
10/2/2026, 5:00:00 AM 100% 1 447ms
10/2/2026, 7:00:00 AM 100% 1 482ms
10/2/2026, 9:00:00 AM 100% 1 437ms
10/2/2026, 11:00:00 AM 100% 1 464ms
10/2/2026, 1:00:00 PM 100% 1 467ms
10/2/2026, 3:00:00 PM 100% 1 437ms
10/2/2026, 5:00:00 PM 100% 1 457ms
10/2/2026, 7:00:00 PM 100% 1 426ms
10/2/2026, 9:00:00 PM 100% 1 442ms
10/2/2026, 11:00:00 PM 100% 1 475ms
10/3/2026, 12:00:00 AM 100% 1 449ms
10/3/2026, 2:00:00 AM 100% 1 452ms
10/3/2026, 4:00:00 AM 100% 1 434ms
10/3/2026, 6:00:00 AM 100% 1 469ms
10/3/2026, 8:00:00 AM 100% 1 467ms
10/3/2026, 10:00:00 AM 100% 1 446ms
10/3/2026, 12:00:00 PM 100% 1 437ms
10/3/2026, 2:00:00 PM 100% 1 153ms
10/3/2026, 3:00:00 PM 100% 1 459ms
10/3/2026, 5:00:00 PM 100% 1 468ms
10/3/2026, 7:00:00 PM 100% 1 473ms
10/3/2026, 9:00:00 PM 100% 1 243ms
10/3/2026, 11:00:00 PM 100% 1 153ms
10/4/2026, 1:00:00 AM 100% 1 157ms
10/4/2026, 2:00:00 AM 100% 1 160ms
10/4/2026, 4:00:00 AM 100% 1 164ms
10/4/2026, 6:00:00 AM 100% 1 163ms
10/4/2026, 8:00:00 AM 100% 1 163ms
10/4/2026, 1:00:00 PM 100% 1 162ms
10/4/2026, 3:00:00 PM 100% 1 160ms
10/4/2026, 5:00:00 PM 100% 1 162ms
10/4/2026, 6:00:00 PM 100% 1 490ms
10/4/2026, 8:00:00 PM 100% 1 150ms
10/5/2026, 2:00:00 AM 100% 1 150ms
10/5/2026, 7:00:00 AM 100% 1 170ms
10/5/2026, 9:00:00 AM 100% 1 159ms
10/5/2026, 11:00:00 AM 100% 1 150ms
10/5/2026, 1:00:00 PM 100% 1 163ms
10/5/2026, 2:00:00 PM 100% 1 148ms
10/5/2026, 4:00:00 PM 100% 1 146ms
10/5/2026, 6:00:00 PM 100% 1 151ms
10/5/2026, 8:00:00 PM 100% 1 149ms
10/5/2026, 10:00:00 PM 100% 1 155ms
57
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
95

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
36

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
3

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
coinbase-cdp
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Infomaniak Network SA
Domain registered
2026-04-01
Hosting network
RLWY-HIKARI-01
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

3
payments (30d)
0.02
USD volume (30d)
2
paying wallets (30d)

Payments per day

last payment 9/29/2026
0 3 5 Sep 6Sep 29
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/6/2026 2 0.01 1
9/29/2026 1 0.01 1

This payout wallet is shared: figures cover all 5 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

https://api.ibanforge.com/v1/iban/validate x402 endpoint