Market / IBANforge
External service · publisher supplied metadata

IBANforge

Source and listing identity

Source: x402 Bazaar

Listing ID: x402:5c8a077a201ee1b96dfd53dd8af27a01a63367a28d9132696148a37a49e59253

Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.

A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.

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+ BIC entries, about two thirds from a public copy of the SWIFT directory frozen in January 2018 · v1.9.0.

APIx402Indexed

Listing completeness · 80/100

Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.

Name and traceable source
10/10 · Present
Meaningful description
10/10 · Present
Connection or installation reference
20/20 · Present
Dedicated documentation or source repository
0/15 · Missing or insufficient
Explicit free access or numeric tariff
20/20 · Present
Declared integration protocol
10/10 · Present
Source updated within 90 days
10/10 · Present
Declared capability names
0/5 · Missing or insufficient

Evaluated 2026-10-30 · Method listing-completeness-1. Scoring rules

Connect & use

Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.

x402 resource

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

Read the current payment requirements with a compatible client before authorizing a call.

Documentation ↗Open provider website ↗

Categories and declared capabilities

Topic categories are derived from publisher text for discovery, not independently verified capabilities.

The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.

Evidence, with its limits.

This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.

The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →