api.ibanforge.com

https://api.ibanforge.com/v1/ch/clearing/:iid

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

Resolve a Swiss BC-Nummer / IID (1-5 digits) into institution name, type, address, BIC, the full payment-rail participation (SIC, RTGS CHF, Instant Payments CHF, euroSIC, LSV+/BDD) and the QR-IID allocation. Backed by 1,100+ SIX BankMaster entries (refreshed monthly) — the canonical Swiss banking source. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) · 1,100+ SIX BankMaster entries, refreshed monthly · v1.4.3.

60
reliability

Reliability & health

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

7 days 30 days

Uptime

60.0% avg
0% 50% 100% Aug 17Aug 18Aug 20Aug 21

Response time

p50 462ms · p95 716ms
0ms 300ms 600ms Aug 17Aug 18Aug 20Aug 21
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/17/2026, 12:00:00 AM 0% 1 —
8/18/2026, 12:00:00 AM 0% 1 —
8/19/2026, 12:00:00 AM 100% 13 563ms
8/20/2026, 12:00:00 AM 100% 21 472ms
8/21/2026, 12:00:00 AM 100% 10 388ms
60
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
96

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

Latency
94

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
66

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 92% — 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
—
Domain registered
—
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)

18
payments (30d)
0.09
USD volume (30d)
2
paying wallets (30d)

Payments per day

last payment 8/18/2026
0 10 20 Jul 29Aug 14Aug 17Aug 18
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
7/29/2026 1 0.01 1
8/14/2026 4 0.03 1
8/17/2026 12 0.05 1
8/18/2026 1 0 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/compliance x402 endpoint https://api.ibanforge.com/v1/bic/:code x402 endpoint https://api.ibanforge.com/v1/iban/validate x402 endpoint https://api.ibanforge.com/v1/iban/batch x402 endpoint