TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-23 · finished 2026-10-23 13:20 UTC
Listed
32,435

verificar jwt pago derived

api.vextorium.comIdentityderived

POST https://api.vextorium.com/verificar-jwt-pago

passlisted in Coinbase#52 by calls of 1,027 on this host

0.003 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-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-24 21:07 UTC · method · pinnable · sweep daily-2026-10-24
Uptime, 7 / 30 / 90 days
83% / 96% / 96%
as of 2026-10-24 21:07 UTC · method · pinnable · 5 of 6 in 7d, 22 of 23 in 30d, 22 of 23 in 90d
Calls, trailing 30 days
3
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
3
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-08 06:09 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-10-02
as of 2026-10-02 22:12 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.003 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
5
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

31 observations, 3 of them a change

How has the volume on this endpoint moved?

12333 Oct4 Oct5 Oct6 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct13 Oct
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-10-03. 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.

In words

api.vextorium.com lists 1,027 endpoints; verificar jwt pago is tied 52nd by calls with 481 others.

Requests carry a json body with the field token.

A response from verificar jwt pago, as declared, includes motivo, valido, cabecera, algoritmo and contenido.

verificar jwt pago drew 3 calls from 3 unique payers in the trailing 30 days, every call from a different payer.

verificar jwt pago was last called 5 days before the snapshot.

A call to verificar jwt pago costs 0.003 USDC on Base, as declared.

verificar jwt pago accepts payment on Base, Solana, Polygon, Optimism and 1 other, 5 options in all, to 2 different wallets.

TOLL files verificar jwt pago under identity: a POST endpoint on api.vextorium.com, listed in the Coinbase registry.

verificar jwt pago answered the sweep of 2026-10-24 with a valid 402, passing 22 of 23 sweeps since 2026-10-02.

Closest in price to verificar jwt pago within identity: domains check at api.clawfetch.ai and risk check at x402check.xyz.

verificar jwt pago is priced above 13% of comparable listings in identity.

Within identity, 57% of endpoints with counters have fewer calls.

For 1 of the options on verificar jwt pago, TOLL has no verified decimals and shows the raw amount.

The wallet paid by verificar jwt pago is the payee of 1,037 endpoints across 3 hosts.

The seller's own tags are jwt, auth, jwks and security.

The price of verificar jwt pago is declared by 116 other listings in identity too.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.003 USDCexact0xb9f06D…b71aCf
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.003 USDCexactHcjfmZLg…yt3pz2
Coinbaseeip155:137USDC0.003 USDCexact0xb9f06D…b71aCf
Coinbaseeip155:10USDC0.003 USDCexact0xb9f06D…b71aCf
Coinbaseeip155:5042GatewayWalletBatched3000 smallest units, decimals unknownexact0xb9f06D…b71aCf

Preflight checks at the last sweep

the checks, as of 2026-10-24 21:07 UTC · method · pinnableendpoint 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-24 21:07 UTCpass0daily-2026-10-24
2026-10-23 06:17 UTCpass0daily-2026-10-23
2026-10-22 04:31 UTCpass0daily-2026-10-22
2026-10-21 08:09 UTCfail1daily-2026-10-21
2026-10-20 08:26 UTCpass0daily-2026-10-20
2026-10-19 06:00 UTCpass0daily-2026-10-19
2026-10-18 08:13 UTCpass0daily-2026-10-18
2026-10-17 18:14 UTCpass0daily-2026-10-17
2026-10-16 04:28 UTCpass0daily-2026-10-16
2026-10-15 06:02 UTCpass0daily-2026-10-15
2026-10-14 04:26 UTCpass0daily-2026-10-14
2026-10-13 08:52 UTCpass0daily-2026-10-13
2026-10-12 06:16 UTCpass0daily-2026-10-12
2026-10-11 04:39 UTCpass0daily-2026-10-11
2026-10-10 09:56 UTCpass0daily-2026-10-10
2026-10-09 04:41 UTCpass0daily-2026-10-09
2026-10-08 06:19 UTCpass0daily-2026-10-08
2026-10-07 05:29 UTCpass0daily-2026-10-07
2026-10-06 06:24 UTCpass0daily-2026-10-06
2026-10-05 06:07 UTCpass0daily-2026-10-05
2026-10-04 08:56 UTCpass0daily-2026-10-04
2026-10-03 04:15 UTCpass0daily-2026-10-03
2026-10-02 22:16 UTCpass0new-after-daily-2026-10-02

Registry presence

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

  1. listed in Coinbase

Declared input and output, as listed

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

The input and output block
{
  "input": {
    "body": {
      "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "motivo": "Sin jwks_url ni secreto: solo decodificado, firma NO verificada.",
      "valido": null,
      "cabecera": {
        "alg": "HS256",
        "typ": "JWT"
      },
      "algoritmo": "HS256",
      "contenido": {
        "iat": 1516239022,
        "sub": "1234567890",
        "name": "John Doe"
      }
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "verificar jwt pago on api.vextorium.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-vextorium-com-verificar-jwt-pago-19ad7d/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-api-vextorium-com-verificar-jwt-pago-19ad7d-2026-10-13T14-08Z,
  author = {TOLL},
  title = {verificar jwt pago on api.vextorium.com},
  howpublished = {\url{https://tollindex.com/e/api-vextorium-com-verificar-jwt-pago-19ad7d/at/2026-10-13T14-08Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 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 verificar jwt pago, 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 19ad7de2b0ca4829d45b2ad38076e67facef97aac6059dfa3a8bb1e02f407e4c from wallet 0xb9f06D2734B7E9D7b21B64C4D8b95bd774b71aCf

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

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