TOLL

What software pays for, recorded every six hours.

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

reparar json pago derived

api.vextorium.comComputederived

POST https://api.vextorium.com/reparar-json-pago

faillisted in Coinbase#17 by calls of 1,027 on this host

0.002 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
fail
as of 2026-10-29 09:18 UTC · method · pinnable · sweep daily-2026-10-29
Uptime, 7 / 30 / 90 days
80% / 96% / 96%
as of 2026-10-29 09:18 UTC · method · pinnable · 4 of 5 in 7d, 23 of 24 in 30d, 23 of 24 in 90d
Calls, trailing 30 days
4
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-03
as of 2026-10-03 05:16 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.002 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

30 observations, 4 of them a change

How has the volume on this endpoint moved?

123443 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

At the sweep of 2026-10-29 it answered HTTP 404 rather than 402, so TOLL records it as failing.

reparar json pago, a POST endpoint on api.vextorium.com, appears in the Coinbase registry; TOLL's taxonomy puts it in compute.

Per call, reparar json pago declares 0.002 USDC on Base.

The listing describes the request as a json body with the field texto.

For reparar json pago the listing declares 5 accepts on Base, Solana, Polygon, Optimism and 1 other, to 2 different wallets.

reparar json pago returns json; the example shows json, objeto, reparado and ya_era_valido.

The registry's counters give reparar json pago 4 calls and 3 unique payers over 30 days.

The most recent call was 5 days before the snapshot.

reparar json pago is one of 1,027 listed endpoints on api.vextorium.com, tied 17th by calls with 34 others among them.

reparar json pago is among the cheapest in compute; 10% of comparable listings ask less.

Closest in price to reparar json pago within compute: fetch at web.cyberwarex.com and paid solana priority fee at api.oblique.markets.

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

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

reparar json pago out-counts 89% of the 1,852 endpoints in compute that carry counters.

The seller's tags on reparar json pago are json, repair, llm and parsing.

The price of reparar json pago is declared by 176 other listings in compute 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.002 USDCexact0xb9f06D…b71aCf
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.002 USDCexactHcjfmZLg…yt3pz2
Coinbaseeip155:137USDC0.002 USDCexact0xb9f06D…b71aCf
Coinbaseeip155:10USDC0.002 USDCexact0xb9f06D…b71aCf
Coinbaseeip155:5042GatewayWalletBatched2000 smallest units, decimals unknownexact0xb9f06D…b71aCf

Preflight checks at the last sweep

the checks, as of 2026-10-29 09:18 UTC · method · pinnableendpoint answered HTTP 404

  • returns_402 · an unauthenticated request gets HTTP 402

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-29 09:18 UTCfail1daily-2026-10-29
2026-10-28 09:40 UTCpass0daily-2026-10-28
2026-10-27 09:23 UTCpass0daily-2026-10-27
2026-10-26 15:50 UTCpass0daily-2026-10-26
2026-10-23 09:38 UTCpass0daily-2026-10-23
2026-10-21 12:07 UTCpass0daily-2026-10-21
2026-10-20 11:45 UTCpass0daily-2026-10-20
2026-10-19 09:24 UTCpass0daily-2026-10-19
2026-10-18 11:14 UTCpass0daily-2026-10-18
2026-10-16 07:25 UTCpass0daily-2026-10-16
2026-10-15 09:14 UTCpass0daily-2026-10-15
2026-10-14 07:14 UTCpass0daily-2026-10-14
2026-10-13 12:00 UTCpass0daily-2026-10-13
2026-10-12 09:24 UTCpass0daily-2026-10-12
2026-10-11 08:04 UTCpass0daily-2026-10-11
2026-10-10 16:11 UTCpass0daily-2026-10-10
2026-10-09 09:00 UTCpass0daily-2026-10-09
2026-10-08 10:28 UTCpass0daily-2026-10-08
2026-10-07 09:53 UTCpass0daily-2026-10-07
2026-10-06 10:38 UTCpass0daily-2026-10-06
2026-10-05 09:31 UTCpass0daily-2026-10-05
2026-10-04 11:44 UTCpass0daily-2026-10-04
2026-10-03 06:20 UTCpass0daily-2026-10-03
2026-10-03 05:19 UTCpass0new-after-daily-2026-10-03

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": {
      "texto": "```json\n{name: 'Ana', 'edad': 30, activo: True, tags: ['a','b',],"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "json": "{\"name\": \"Ana\", \"edad\": 30, \"activo\": true, \"tags\": [\"a\", \"b\"]}",
      "objeto": {
        "edad": 30,
        "name": "Ana",
        "tags": [
          "a",
          "b"
        ],
        "activo": true
      },
      "reparado": true,
      "ya_era_valido": false
    }
  }
}
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, "reparar json pago on api.vextorium.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-vextorium-com-reparar-json-pago-886896/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-api-vextorium-com-reparar-json-pago-886896-2026-10-13T14-08Z,
  author = {TOLL},
  title = {reparar json pago on api.vextorium.com},
  howpublished = {\url{https://tollindex.com/e/api-vextorium-com-reparar-json-pago-886896/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 reparar json 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 88689629e9329da9ee4346f123678cccafe1643726b238c08e054a73eaf6e9e9 from wallet 0xb9f06D2734B7E9D7b21B64C4D8b95bd774b71aCf

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

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