bic derived

api.ibanforge.comOther derived

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

passabsent from every registrycounted above 83% of Other

0.003 USDC

per call, as the listing declares it on eip155:8453

Compare with another Every figure as JSON Cite this page

the price, as of 2026-10-01 05:50 UTC · method

Validation state: pass; as of 2026-10-01 08:28 UTC · method · sweep daily-2026-10-01
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-10-01 08:28 UTC · method · 4 of 4 in 7d, 16 of 16 in 30d, 16 of 16 in 90d
Calls, trailing 30 days: 3; as of 2026-10-01 05:50 UTC · method
Unique payers, trailing 30 days: 1; as of 2026-10-01 05:50 UTC · method
Last called: 2026-09-01 08:20 UTC; as of 2026-10-01 05:50 UTC · method
First observed by TOLLderived: 2026-09-10; as of 2026-09-10 19:08 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived: 0.003 USDC; as of 2026-10-01 05:50 UTC · method · on eip155:8453
Networks: 1; as of 2026-10-01 05:50 UTC · method

Counters

86 observations, 3 of them a change, and no more: the endpoint is absent from every registry

How has the volume on this endpoint moved?

Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10 and ending at 2026-10-01, the last snapshot that carried it. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot. The series is final; nothing will be added to it.

In words

TOLL files bic under the "other" category: a GET endpoint on api.ibanforge.com, listed in neither registry at the last pull.

bic is priced at 0.003 USDC on Base.

The request to bic is the path parameter code.

bic returns json; the example shows bic, lei, bic8, city, bic11, found and 2 others.

The daily sweep got a valid payment challenge from bic on 2026-10-01, as at every sweep since 2026-09-11.

bic is the only listed endpoint on api.ibanforge.com.

One payer accounts for all 3 calls to bic over 30 days.

The last call to bic came 30 days before the snapshot, 2026-09-01.

Closest in price to bic within the "other" category: convert weight at weight402endpoint.vercel.app and stats at uptime.cyberwarex.com.

bic is priced above 41% of comparable listings in the "other" category.

bic out-counts 83% of the 3,605 endpoints in the "other" category that carry counters.

The wallet paid by bic is the payee of 5 endpoints on one host.

The seller's own tags are iban, bic, sepa and compliance.

bic was missing from the Coinbase registry at the pull of 2026-10-01, not yet confirmed by a second pull; that is registry presence, not liveness.

The price of bic is declared by 62 other listings in the "other" category too.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-10-01 05:50 UTC · method

Every payment option declared on this listing
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	0.003 USDC	exact	0xD13bD0…B40a55

Preflight checks at the last sweep

the checks, as of 2026-10-01 08:28 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTC	state	sweep
2026-10-01 08:28 UTC	pass	daily-2026-10-01
2026-09-30 07:50 UTC	pass	daily-2026-09-30
2026-09-29 20:03 UTC	pass	daily-2026-09-29
2026-09-28 17:07 UTC	pass	daily-2026-09-28
2026-09-23 07:05 UTC	pass	daily-2026-09-23
2026-09-22 07:17 UTC	pass	daily-2026-09-22
2026-09-21 07:40 UTC	pass	daily-2026-09-21
2026-09-19 05:41 UTC	pass	daily-2026-09-19
2026-09-18 14:12 UTC	pass	daily-2026-09-18
2026-09-17 05:33 UTC	pass	daily-2026-09-17
2026-09-16 05:33 UTC	pass	daily-2026-09-16
2026-09-15 05:50 UTC	pass	daily-2026-09-15
2026-09-14 05:22 UTC	pass	daily-2026-09-14
2026-09-13 05:18 UTC	pass	daily-2026-09-13
2026-09-12 07:34 UTC	pass	daily-2026-09-12
2026-09-11 11:21 UTC	pass	daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

2026-10-01 13:10 UTCabsent from Coinbase at this pull
2026-09-10 19:08 UTClisted in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-09-01 08:20 UTC · method

The input and output block

{
  "input": {
    "type": "http",
    "method": "GET",
    "pathParams": {
      "code": "CHASUS33"
    },
    "discoverable": true
  },
  "output": {
    "type": "json",
    "example": {
      "bic": "UBSWCHZH80A",
      "lei": "549300WOIFUSNYH0FL22",
      "bic8": "UBSWCHZH",
      "city": "Zurich",
      "bic11": "UBSWCHZH80A",
      "found": true,
      "source": "gleif",
      "address": {
        "city": "Zurich",
        "type": "registered",
        "source": "GLEIF",
        "street": "Bahnhofstrasse 45",
        "country": "CH",
        "post_code": "8001"
      },
      "country": {
        "code": "CH",
        "name": "Switzerland"
      },
      "lei_status": "ACTIVE",
      "branch_code": "80A",
      "institution": "UBS Switzerland AG",
      "is_test_bic": false,
      "valid_format": true,
      "_example_notice": "ILLUSTRATIVE SAMPLE — these are demo values for a fixed record, NOT the data for the resource you requested. Do not report them to a user. Authenticate (Authorization: Bearer ifk_...) or pay via x402 to get the real response.",
      "address_available": true
    }
  }
}

What the listing says

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.

the record, 2026-09-01 08:20 UTC · method

As declared

GET
eip155:8453
USDC
exact

Every tag is a field on the listing, not a keyword TOLL assigned.

Who is paid

0xD13bD0…B40a55

Takes payment for 5 endpoints on 1 host.

Among Other

counted above83%

of 3,605 that carry counters

cheaper than41%

of 3,605 with a comparable price

3,678 endpoints are in this category. 62 declare exactly this price.

the comparison, 2026-10-01 13:10 UTC · method · live

Nearest on price

brokenkeyremapperlinkbrokenkey-api-link-tau.vercel.app0.003 USDCpass
convert weightweight402endpoint.vercel.app0.0025 USDCpass
statsuptime.cyberwarex.com0.002 USDCpass
x402 testsandbox.node4all.com0.002 USDCpass
enrich profilewin.oneshotagent.com0.005 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-10-01 13:10 UTC · method · live

Elsewhere in the record

Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "bic on api.ibanforge.com". https://tollindex.com/e/api-ibanforge-com-v1-bic-code-8f15f6. Accessed [access date].

BibTeX

@misc{toll-e-api-ibanforge-com-v1-bic-code-8f15f6-2026-10-01,
  author = {TOLL},
  title = {bic on api.ibanforge.com},
  howpublished = {\url{https://tollindex.com/e/api-ibanforge-com-v1-bic-code-8f15f6}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-01 13:10 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about bic, or reply as the named seller