TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 16:57 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,167

capabilities openapi agent readiness derived

api.vrsai.techInferencederived

POST https://api.vrsai.tech/v1/capabilities/openapi_agent_readiness

passlisted in Coinbase#3 by calls of 6 on this host

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-09-15 16:57 UTC · method · pinnable

Validation state
pass
as of 2026-09-15 06:06 UTC · method · pinnable · sweep daily-2026-09-15
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-09-15 06:06 UTC · method · pinnable · 5 of 5 in 7d, 5 of 5 in 30d, 5 of 5 in 90d
Calls, trailing 30 days
3
as of 2026-09-15 16:57 UTC · method · pinnable
Unique payers, trailing 30 days
2
as of 2026-09-15 16:57 UTC · method · pinnable
Last called
2026-09-03 18:51 UTC
as of 2026-09-15 16:57 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.03 USDC
as of 2026-09-15 16:57 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-09-15 16:57 UTC · method · pinnable

Counters

28 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,297 endpoints in Inference that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 3: 423 in the category are counted higher and 1,873 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 28 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.vrsai.tech, capabilities openapi agent readiness takes POST requests, is listed in the Coinbase registry, and falls under inference by TOLL's rules.

On Base, capabilities openapi agent readiness asks 0.03 USDC per call.

Callers of capabilities openapi agent readiness supply a json body with the field document.

For capabilities openapi agent readiness the listing declares 2 accepts on Base and Solana, to 2 different wallets.

A response from capabilities openapi agent readiness, as declared, includes score, summary, verdict, findings, dimensions, openapi_version and 1 other.

capabilities openapi agent readiness answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.

capabilities openapi agent readiness shares api.vrsai.tech with 5 other listed endpoints and is tied 3rd by calls with 3 others.

capabilities openapi agent readiness takes 14% of the calls counted across api.vrsai.tech.

The registry's counters give capabilities openapi agent readiness 3 calls and 2 unique payers over 30 days.

capabilities openapi agent readiness was last called 12 days before the snapshot.

Closest in price to capabilities openapi agent readiness within inference: chat completions at agent402.tools and check blacklist at x402.cloudpulsepoint.com.

capabilities openapi agent readiness is priced above 69% of comparable listings in inference.

Within inference, 75% of endpoints with counters have fewer calls.

The wallet paid by capabilities openapi agent readiness is the payee of 6 endpoints on one host.

The seller's tags on capabilities openapi agent readiness are openapi, agent-readiness, api-contract and llm-tools.

40 other listings in inference declare exactly the same price.

Payment options as declared

the payment options, as of 2026-09-15 16:57 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.03 USDCexact0x6746dF…bA09Af
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.03 USDCexactEiJRESZj…4xFocj

Preflight checks at the last sweep

the checks, as of 2026-09-15 06:06 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-09-15 06:06 UTCpass0daily-2026-09-15
2026-09-14 05:37 UTCpass0daily-2026-09-14
2026-09-13 05:31 UTCpass0daily-2026-09-13
2026-09-12 07:48 UTCpass0daily-2026-09-12
2026-09-11 11:40 UTCpass0daily-2026-09-11

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-09-03 18:51 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "document": {
        "info": {
          "title": "Status API",
          "version": "1.0.0"
        },
        "paths": {
          "/status": {
            "get": {
              "responses": {
                "200": {
                  "content": {
                    "application/json": {
                      "schema": {
                        "type": "object",
                        "required": [
                          "status"
                        ],
                        "properties": {
                          "status": {
                            "type": "string"
                          }
                        }
                      }
                    }
                  },
                  "description": "Current status."
                }
              },
              "description": "Return current service status.",
              "operationId": "getStatus"
            }
          }
        },
        "openapi": "3.1.0",
        "servers": [
          {
            "url": "https://status.example.org"
          }
        ]
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "score": 100,
      "summary": {
        "paths": 1,
        "schemas": 0,
        "findings": 0,
        "operations": 1,
        "findings_truncated": false
      },
      "verdict": "ready",
      "findings": [],
      "dimensions": [
        {
          "id": "structure_and_version",
          "score": 15,
          "max_score": 15
        },
        {
          "id": "operation_semantics",
          "score": 20,
          "max_score": 20
        },
        {
          "id": "request_contracts",
          "score": 20,
          "max_score": 20
        },
        {
          "id": "response_contracts",
          "score": 20,
          "max_score": 20
        },
        {
          "id": "authentication_and_access",
          "score": 10,
          "max_score": 10
        },
        {
          "id": "machine_operability",
          "score": 15,
          "max_score": 15
        }
      ],
      "openapi_version": "3.1.0",
      "ruleset_version": "1.1.1"
    }
  }
}
Cite this page

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

Plain text

TOLL, "capabilities openapi agent readiness on api.vrsai.tech", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-vrsai-tech-v1-capabilities-openapi-agent-readiness-a5ceea/at/2026-09-15T16-57Z. Accessed [access date].

BibTeX

@misc{toll-e-api-vrsai-tech-v1-capabilities-openapi-agent-readiness-a5ceea-2026-09-15T16-57Z,
  author = {TOLL},
  title = {capabilities openapi agent readiness on api.vrsai.tech},
  howpublished = {\url{https://tollindex.com/e/api-vrsai-tech-v1-capabilities-openapi-agent-readiness-a5ceea/at/2026-09-15T16-57Z}},
  year = {2026},
  month = {9},
  note = {Pinned view of the snapshot of 2026-09-15 16:57 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 capabilities openapi agent readiness, 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 a5ceeab28ffb349ba724e278dddb69ed4eedec67b07ff2eaa44d79c497591ad8 from wallet 0x6746dFF7bDB1ED4940DBe50024795AD97CbA09Af

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

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