TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-19 · finished 2026-10-19 12:59 UTC
Listed
32,435

iban compliance derived

api.ibanforge.comIdentityderived

POST https://api.ibanforge.com/v1/iban/compliance

passabsent from every registrycounted above 0% of Identity

0.02 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-09-16 04:48 UTC · method

Validation state
pass
as of 2026-09-16 06:02 UTC · method · sweep daily-2026-09-16
Uptime, 7 / 30 / 90 days
— / — / 100%
as of 2026-09-16 06:02 UTC · method · 0 of 0 in 7d, 0 of 0 in 30d, 6 of 6 in 90d
Calls, trailing 30 days
1
as of 2026-09-16 04:48 UTC · method
Unique payers, trailing 30 days
1
as of 2026-09-16 04:48 UTC · method
Last called
2026-08-17 05:18 UTC
as of 2026-09-16 04:48 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.02 USDC
as of 2026-09-16 04:48 UTC · method · on eip155:8453
Networks
1
as of 2026-09-16 04:48 UTC · method

Counters

30 observations, 1 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 2,150 endpoints in Identity that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 1,412 in the category are counted higher and 737 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 30 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.

In words

At api.ibanforge.com, iban compliance takes POST requests, is listed in neither registry at the last pull, and falls under identity by TOLL's rules.

iban compliance is priced at 0.02 USDC on Base.

Requests carry a json body with the field iban.

iban compliance returns json; the example shows bic, iban, meta, valid, country, compliance and 1 other.

iban compliance answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-11.

iban compliance is the only listed endpoint on api.ibanforge.com.

In the trailing 30 days: one call, one payer.

iban compliance was last called 57 days before the snapshot.

Closest in price to iban compliance within identity: decide at agent402.tools and contract at oracle.cyberwarex.com.

Among comparable prices in identity, iban compliance sits above 69% of them.

5 listed endpoints on one host pay to the same wallet.

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

iban compliance was missing from the Coinbase registry at the pull of 2026-09-16, confirmed at the pull of 2026-09-16; that is registry presence, not liveness.

The price of iban compliance is declared by 190 other listings in identity 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-09-16 04:48 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.02 USDCexact0xD13bD0…B40a55

Preflight checks at the last sweep

the checks, as of 2026-09-16 06:02 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, UTCstatefailed checkssweep
2026-09-16 06:02 UTCpass0daily-2026-09-16
2026-09-15 06:18 UTCpass0daily-2026-09-15
2026-09-14 05:49 UTCpass0daily-2026-09-14
2026-09-13 05:42 UTCpass0daily-2026-09-13
2026-09-12 07:59 UTCpass0daily-2026-09-12
2026-09-11 11:54 UTCpass0daily-2026-09-11

Registry presence

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

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-08-17 05:18 UTC · method

The input and output block
{
  "input": {
    "body": {
      "iban": "CH1000230000000012345"
    },
    "type": "http",
    "method": "POST",
    "schema": {
      "type": "object",
      "required": [
        "iban"
      ],
      "properties": {
        "iban": {
          "type": "string",
          "maxLength": 34,
          "minLength": 15,
          "description": "IBAN to triage."
        }
      }
    },
    "bodyType": "json",
    "discoverable": true
  },
  "output": {
    "type": "json",
    "example": {
      "bic": {
        "city": "Zürich",
        "code": "UBSWCHZH",
        "bank_name": "UBS Switzerland AG"
      },
      "iban": "CH1000230000000012345",
      "meta": {
        "scope": "bank_bic_only"
      },
      "valid": true,
      "country": {
        "code": "CH",
        "name": "Switzerland"
      },
      "compliance": {
        "vop": {
          "status": "not_found",
          "participant": false
        },
        "flags": [
          "no_vop"
        ],
        "sanctions": {
          "fatf_status": "member",
          "matched_lists": [],
          "bank_sanctioned": false,
          "country_sanctioned": false
        },
        "risk_level": "low",
        "risk_score": 5,
        "reachability": {
          "sct": true,
          "sdd": true,
          "sepa_instant": 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."
    }
  }
}
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, "iban compliance on api.ibanforge.com". https://tollindex.com/e/api-ibanforge-com-v1-iban-compliance-b71080. Accessed [access date].

BibTeX

@misc{toll-e-api-ibanforge-com-v1-iban-compliance-b71080-2026-10-13,
  author = {TOLL},
  title = {iban compliance on api.ibanforge.com},
  howpublished = {\url{https://tollindex.com/e/api-ibanforge-com-v1-iban-compliance-b71080}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-13 14:08 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 iban compliance, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint b7108036f12db89d8a5d7c89ed3f5ce61ecbf0c7200a57a3148779f4ec152568 from wallet 0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.