63trust / 100

Uuid Inspect

by JSON and Data Tools in Developer tools

x402 APIPassing, checked 6 h ago

Validate a UUID and read its version, variant and, for v1 and v7, the embedded timestamp.

GET
https://json-data-tools.x402tookit.com/uuid-inspect
Price
$0.02
per call in USDC
Uptime
70.0%
last 30 days
Response time
543 ms
1.1 s slowest 5%
Last check
Passed
6 h ago, next in 26 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://json-data-tools.x402tookit.com/uuid-inspect

Each call costs $0.02 in USDC on Polygon, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://json-data-tools.x402tookit.com/uuid-inspect?uuid=018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80

Parameters

ParameterTypeRequiredDescription
uuidstringYesThe UUID

Example response

The provider's example. We can't check it without paying.

{
  "asOf": "2026-10-11T04:24:45.444Z",
  "canonical": "018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80",
  "degraded": false,
  "disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
  "notChecked": [
    "whether the UUID was ever generated or is unique"
  ],
  "reasons": [],
  "source": "computed locally",
  "summary": "UUID 018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80: version 7, variant RFC 4122/9562, timestamp 2024-05-02T21:03:24.714Z.",
  "timestamp": "2024-05-02T21:03:24.714Z",
  "variant": "RFC 4122/9562",
  "verdict": "VALID",
  "version": 7
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://json-data-tools.x402tookit.com/uuid-inspect?uuid=018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://json-data-tools.x402tookit.com/uuid-inspect?uuid=018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fjson-data-tools.x402tookit.com%2Fuuid-inspect
const res = await pay("https://json-data-tools.x402tookit.com/uuid-inspect?uuid=018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://json-data-tools.x402tookit.com/uuid-inspect?uuid=018f3b1e-7c2a-7d3f-8a11-2b4c5d6e7f80")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
6 h agoPassed402537 ms$0.02
19 h agoPassed402568 ms$0.02
32 h agoPassed402558 ms$0.02
44 h agoExpected HTTP 402, got 530530191 ms-
2 days agoPassed402543 ms$0.02
Show 10 older checks
3 days agoPassed402496 ms$0.02
3 days agoExpected HTTP 402, got 530530106 ms-
4 days agoPassed402770 ms$0.02
4 days agoExpected HTTP 402, got 530530136 ms-
5 days agoExpected HTTP 402, got 530530121 ms-
5 days agoPassed402538 ms$0.02
5 days agoExpected HTTP 402, got 530530224 ms-
5 days agoExpected HTTP 402, got 530530225 ms-
5 days agoPassed402497 ms$0.02
6 days agoPassed402506 ms$0.02