TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 21:59 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
52,265

x402 payment requirement conformance derived

api.zfinia.comMarket dataderived

POST https://api.zfinia.com/x402/v1/x402-payment-requirement-conformance

passabsent from every registry#6 by calls of 15 on this host

0.1 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-04 21:22 UTC · method

Validation state
pass
as of 2026-10-04 14:51 UTC · method · sweep daily-2026-10-04
Uptime, 7 / 30 / 90 days
— / 50% / 50%
as of 2026-10-04 14:51 UTC · method · 0 of 0 in 7d, 1 of 2 in 30d, 1 of 2 in 90d
Calls, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Unique payers, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Last called
2026-10-04 08:05 UTC
as of 2026-10-04 21:22 UTC · method
First observed by TOLLderived
2026-10-04
as of 2026-10-04 12:19 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.1 USDC
as of 2026-10-04 21:22 UTC · method · on eip155:8453
Networks
1
as of 2026-10-04 21:22 UTC · method

Counters

2 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 10,493 endpoints in Market data 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: 7,829 in the category are counted higher and 2,663 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 2 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

Of api.zfinia.com's 15 listings, x402 payment requirement conformance ranks tied 6th by calls with 10 others.

Callers of x402 payment requirement conformance supply a json body with the fields challenge and expected_url.

A response from x402 payment requirement conformance, as declared, includes limits, passed, accepts, version, complete, findings and 2 others.

x402 payment requirement conformance drew a single call from a single payer in the trailing 30 days.

The last call to x402 payment requirement conformance came 29 days before the snapshot, 2026-10-04.

x402 payment requirement conformance is priced at 0.1 USDC on Base.

It accounts for 3% of the calls counted across the host.

TOLL files x402 payment requirement conformance under market data: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.

x402 payment requirement conformance answered the sweep of 2026-10-04 with a valid 402, passing 1 of 2 sweeps since 2026-10-04.

Closest in price to x402 payment requirement conformance within market data: q verdict resource at www.ax1.vc and activities smarttraders smartmoney at x402.sniperx.fun.

x402 payment requirement conformance is near the top of prices in market data; 92% of comparable listings are cheaper.

The wallet paid by x402 payment requirement conformance is the payee of 179 endpoints across 5 hosts.

Seller tags: x402, machine payments, conformance and preflight.

x402 payment requirement conformance was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; that is registry presence, not liveness.

The price of x402 payment requirement conformance is declared by 314 other listings in market data 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-04 21:22 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.1 USDCexact0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-04 14:51 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-10-04 14:51 UTCpass0daily-2026-10-04
2026-10-04 12:52 UTCfail1new-after-daily-2026-10-04

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-10-04 08:05 UTC · method

The input and output block
{
  "input": {
    "body": {
      "challenge": {
        "accepts": [
          {
            "asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
            "payTo": "0xa1b2c30000000000000000000000000000009f8e",
            "amount": "5000",
            "scheme": "exact",
            "network": "eip155:8453"
          },
          {
            "asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
            "payTo": "0xa1b2c30000000000000000000000000000009f8e",
            "amount": "25000",
            "scheme": "exact",
            "network": "eip155:8453"
          }
        ],
        "resource": {
          "url": "https://api.merchant.test/v1/other",
          "mimeType": "application/json",
          "description": "Scoring"
        },
        "extensions": {
          "bazaar": {
            "schema": {
              "properties": {
                "input": {
                  "type": "object"
                }
              }
            }
          }
        },
        "x402Version": 2
      },
      "expected_url": "https://api.merchant.test/v1/score"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "limits": {
        "maxAssets": 100,
        "maxAccepts": 20,
        "maxFindings": 500,
        "maxNetworks": 50,
        "maxResources": 500,
        "maxChallenges": 200
      },
      "passed": false,
      "accepts": [
        {
          "asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
          "amount": "5000",
          "pay_to": "0xa1b2c30000000000000000000000000000009f8e",
          "scheme": "exact",
          "network": "eip155:8453"
        },
        {
          "asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
          "amount": "25000",
          "pay_to": "0xa1b2c30000000000000000000000000000009f8e",
          "scheme": "exact",
          "network": "eip155:8453"
        }
      ],
      "version": 2,
      "complete": true,
      "findings": [
        {
          "code": "OUTPUT_SCHEMA_MISSING",
          "detail": "OUTPUT_SCHEMA_MISSING does not stop a payment but makes the call harder to construct correctly.",
          "severity": "advisory"
        },
        {
          "code": "RESOURCE_NOT_BOUND_TO_ENDPOINT",
          "detail": "The challenge names https://api.merchant.test/v1/other and it was served from https://api.merchant.test/v1/score, so paying it would satisfy a requirement for a different resource.",
          "severity": "blocking"
        },
        {
          "code": "OUTPUT_SCHEMA_MISSING",
          "detail": "No output schema is declared, so a caller cannot type the result.",
          "severity": "advisory"
        }
      ],
      "request_id": "example-request",
      "service_id": "x402_payment_requirement_conformance",
      "assumptions": [
        "Nothing is fetched and nothing is paid. payment_sent is false on every response and is a constant, not a measurement.",
        "A blocking defect stops a payment being constructed at all; an advisory one makes the call harder to get right. Only the first kind means do not attempt this.",
        "payable_now is a statement about the challenge, never a promise that a payment would succeed."
      ],
      "limitations": [
        "Conformance of the challenge supplied. Whether the endpoint honours it, whether the price is fair, and whether the payee is who they claim are all outside what a challenge can show.",
        "Without expected_url the resource binding is not checked, and payable_now is false in that case because an unchecked binding cannot read as safe."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "payable_now": false,
      "not_examined": [],
      "payment_sent": false,
      "resource_url": "https://api.merchant.test/v1/other",
      "finding_count": 4,
      "declared_input": {
        "type": "object"
      },
      "declared_output": null,
      "service_version": "1.0.0",
      "findings_by_code": {
        "ACCEPTS_PRICE_SPREAD": 1,
        "OUTPUT_SCHEMA_MISSING": 2,
        "RESOURCE_NOT_BOUND_TO_ENDPOINT": 1
      },
      "advisory_warnings": [
        "OUTPUT_SCHEMA_MISSING"
      ],
      "blocking_warnings": [],
      "resource_is_object": true
    }
  }
}
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, "x402 payment requirement conformance on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-x402-payment-requirement-conformance-e6cdfc. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-x402-payment-requirement-conformance-e6cdfc-2026-11-01,
  author = {TOLL},
  title = {x402 payment requirement conformance on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-x402-payment-requirement-conformance-e6cdfc}},
  year = {2026},
  month = {11},
  note = {Frozen at its last observation, 2026-11-01 21:59 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 x402 payment requirement conformance, 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 e6cdfcafdb6fdfbe46ba22e666d5a25a83fecb072705dbb9a65c1a4635ec9bd7 from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

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

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