TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 00:37 UTC
Sweep
daily-2026-10-12 · finished 2026-10-12 13:00 UTC
Listed
33,700

guard allowance derived

allowance.schemasure.comMarket dataderived

POST https://allowance.schemasure.com/v1/guard/allowance

passlisted in Coinbasecounted above 95% of Market data

0.03 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 00:37 UTC · method · pinnable

Validation state
pass
as of 2026-10-12 09:44 UTC · method · pinnable · sweep daily-2026-10-12
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-12 09:44 UTC · method · pinnable · 7 of 7 in 7d, 19 of 19 in 30d, 19 of 19 in 90d
Calls, trailing 30 days
27
as of 2026-10-13 00:37 UTC · method · pinnable
Unique payers, trailing 30 days
2
as of 2026-10-13 00:37 UTC · method · pinnable
Last called
2026-10-11 07:38 UTC
as of 2026-10-13 00:37 UTC · method · pinnable
First observed by TOLLderived
2026-09-19
as of 2026-09-19 20:39 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.03 USDC
as of 2026-10-13 00:37 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-10-13 00:37 UTC · method · pinnable

Counters

76 observations, 22 of them a change

How has the volume on this endpoint moved?

-01020302720 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct2 Oct3 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-09-20. 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

allowance.schemasure.com serves guard allowance, a POST endpoint that TOLL places in market data, listed in the Coinbase registry.

On Base, guard allowance asks 0.03 USDC per call.

Callers of guard allowance supply a json body with the field calldata.

A response from guard allowance, as declared, includes ok, result, verdict, evidence, warnings, confidence and 2 others.

guard allowance answered the sweep of 2026-10-12 with a valid 402, as at every sweep since 2026-09-20.

guard allowance is the only listed endpoint on allowance.schemasure.com.

The registry's counters give guard allowance 27 calls and 2 unique payers over 30 days, about 14 calls per payer.

The last call to guard allowance came 2 days before the snapshot, 2026-10-11.

Closest in price to guard allowance within market data: analyze at svm402.com and q verdict resource at www.ax1.vc.

guard allowance is priced above 82% of comparable listings in market data.

Across market data, 9,124 endpoints carry counters and guard allowance out-counts 95% of them.

The wallet paid by guard allowance is the payee of 11 endpoints across 10 hosts.

Seller tags: allowance, approve, revoke and erc20.

The price of guard allowance is declared by 223 other listings in market data too.

Payment options as declared

the payment options, as of 2026-10-13 00:37 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.03 USDCexact0x9876af…612690

Preflight checks at the last sweep

the checks, as of 2026-10-12 09:44 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-12 09:44 UTCpass0daily-2026-10-12
2026-10-11 08:22 UTCpass0daily-2026-10-11
2026-10-10 16:31 UTCpass0daily-2026-10-10
2026-10-09 09:28 UTCpass0daily-2026-10-09
2026-10-08 10:53 UTCpass0daily-2026-10-08
2026-10-07 10:18 UTCpass0daily-2026-10-07
2026-10-06 11:02 UTCpass0daily-2026-10-06
2026-10-05 09:49 UTCpass0daily-2026-10-05
2026-10-04 11:59 UTCpass0daily-2026-10-04
2026-10-03 06:32 UTCpass0daily-2026-10-03
2026-10-02 15:44 UTCpass0daily-2026-10-02
2026-10-01 08:33 UTCpass0daily-2026-10-01
2026-09-30 07:56 UTCpass0daily-2026-09-30
2026-09-29 20:08 UTCpass0daily-2026-09-29
2026-09-28 17:12 UTCpass0daily-2026-09-28
2026-09-23 07:09 UTCpass0daily-2026-09-23
2026-09-22 07:21 UTCpass0daily-2026-09-22
2026-09-21 07:44 UTCpass0daily-2026-09-21
2026-09-20 18:22 UTCpass0new-after-daily-2026-09-19

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-11 07:38 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "calldata": {
        "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "data": "0x095ea7b30000000000000000000000002626664c2603336e57b271c5c0b26f421741e4810000000000000000000000000000000000000000000000000000000000000000",
        "from": "0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4"
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "ok": true,
      "result": {
        "rpc": {
          "endpoints": [],
          "reachable": null,
          "configured": false
        },
        "chain": "eip155:8453",
        "delta": {
          "detail": "this sets the allowance to zero, which cannot increase exposure whatever it is now; the value being replaced could not be read, so whether it is a reduction or already zero is unknown",
          "direction": "unknown",
          "difference": null,
          "increases_exposure": false
        },
        "token": {
          "detail": "no RPC configured, so code presence could not be read; no RPC configured, so token metadata could not be read",
          "symbol": null,
          "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "decimals": null,
          "has_code": null,
          "code_size": null,
          "is_erc721": null,
          "total_supply": null
        },
        "decode": {
          "source": "bundled-abi",
          "selector": "0x095ea7b3",
          "signature": "approve(address,uint256)",
          "candidates": []
        },
        "current": {
          "amount": null,
          "detail": "no RPC endpoint is configured, so the allowance this spender already holds could not be read",
          "source": "unreadable",
          "expiration": null
        },
        "request": {
          "kind": "erc20_approve",
          "mode": "absolute",
          "owner": "0x9f2C5E4a8DB1C3A7e6b0d4f8C1e2A5b7d9c0E3f4",
          "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "amount": "0",
          "target": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "spender": "0x2626664c2603336E57B271c5C0b26F421741e481",
          "summary": "Revoke 0x2626664c2603336E57B271c5C0b26F421741e481's allowance on token 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 by setting it to zero.",
          "deadline": null,
          "token_id": null,
          "expiration": null
        },
        "spender": {
          "proxy": {
            "kind": "unknown",
            "admin": null,
            "beacon": null,
            "detail": "no RPC endpoint is configured, so no slot could be read",
            "address": "0x2626664c2603336E57B271c5C0b26F421741e481",
            "upgradeable": null,
            "slots_probed": [],
            "implementation": null
          },
          "detail": "no RPC endpoint is configured, so it is unknown whether the spender has code",
          "address": "0x2626664c2603336E57B271c5C0b26F421741e481",
          "is_contract": null
        },
        "input_shape": "calldata",
        "denylist_hits": [],
        "classification": {
          "basis": "the allowance is zero, which is bounded without reference to the token's supply",
          "scope": "bounded",
          "subject": "resulting_allowance",
          "total_supply": null,
          "supply_checked": true,
          "resulting_allowance": "0"
        }
      },
      "verdict": "allow",
      "evidence": [
        {
          "code": "CURRENT_ALLOWANCE_UNREADABLE",
          "detail": "The allowance 0x2626664c2603336E57B271c5C0b26F421741e481 already holds could not be read: no RPC endpoint is configured, so the allowance this spender already holds could not be read. Whether this request adds to an existing allowance or replaces one is therefore unknown. It does not change the answer: this request cannot increase what the spender can move.",
          "source": "rpc",
          "severity": "info"
        },
        {
          "code": "SPENDER_CODE_UNREADABLE",
          "detail": "Whether 0x2626664c2603336E57B271c5C0b26F421741e481 is a contract or an account could not be determined: no RPC endpoint is configured, so it is unknown whether the spender has code. It does not change the answer: this request cannot increase what the spender can move.",
          "source": "rpc",
          "severity": "info"
        },
        {
          "code": "SPENDER_PROXY_OPAQUE",
          "detail": "The code that would execute on 0x2626664c2603336E57B271c5C0b26F421741e481's behalf could not be resolved: no RPC endpoint is configured, so no slot could be read. An allowance to a contract whose executing code is unknown is an allowance to unknown code. It does not change the answer: this request cannot increase what the spender can move.",
          "source": "rpc",
          "severity": "info"
        }
      ],
      "warnings": [],
      "confidence": 1,
      "risk_codes": [],
      "request_hash": "sha256:a88cb1eea90d411505068349493a5cf35a1f2b46f4cbb4185330ffd4094c65fb",
      "data_versions": {
        "chain": "eip155:8453",
        "policy": "2026-09-19",
        "denylist": "2026-08-03.1",
        "abi_packs": "2026-08-03.1",
        "signature_index": "2026-08-03.1",
        "allowance_sentinels": "4"
      },
      "policy_version": "2026-09-19"
    }
  }
}
Cite this page

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

Plain text

TOLL, "guard allowance on allowance.schemasure.com", snapshot of 2026-10-13 00:37 UTC. https://tollindex.com/e/allowance-schemasure-com-v1-guard-allowance-94788d/at/2026-10-13T00-37Z. Accessed [access date].

BibTeX

@misc{toll-e-allowance-schemasure-com-v1-guard-allowance-94788d-2026-10-13T00-37Z,
  author = {TOLL},
  title = {guard allowance on allowance.schemasure.com},
  howpublished = {\url{https://tollindex.com/e/allowance-schemasure-com-v1-guard-allowance-94788d/at/2026-10-13T00-37Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-13 00:37 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 guard allowance, 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 94788df46d29243532e827dd6c9bb44c11fae5024120644d73dd8f9a53c96ae2 from wallet 0x9876af0F6D8Ed5155Cd02d1ca56D128601612690

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

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