ToolVet
77trust / 100

Screenshot Evidence Check File

by Screenshot Evidence Check in Documents & files

x402 APIPassing, checked 5 min ago

Screenshot Evidence Check — Reads a description of how a web page was captured or measured - a headless browser capture with a window size, a tall screenshot, a document width reading, a local Lighthouse run, a PageSpeed Insights run, an automation session that has been open for hours, a command-line download size on Windows - and says what that evidence proves, what it cannot prove and the one measurement that would decide, answered as JSON with a verdict. Knows the ways the capture itself pro…

GET https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
418 ms typical, 540 ms slowest 5%
Last check
5 min ago
Next check
in 24 min

How to call it

GET https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file

Each call costs $0.03 in USDC on Base, 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

The listing has no example input.

GET https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file

Example response

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

{
  "file": {
    "content": "<the SKILL.md file>",
    "encoding": "utf-8",
    "name": "SKILL.md"
  },
  "name": "Screenshot Evidence Check",
  "ok": true,
  "receipt": {
    "settled": true,
    "tx": "0x<settlement transaction>"
  },
  "redownload": {
    "token": "<64 hex chars>",
    "url": "<api>/v1/purchases/<token>"
  },
  "sha256": "<sha256 of SKILL.md>",
  "skill": "screenshot-evidence-check",
  "version": "1.0.0"
}

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.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file'

# 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://api.aiskills402.com/v1/skills/screenshot-evidence-check/file' \
  | 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.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
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.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.aiskills402.com%2Fv1%2Fskills%2Fscreenshot-evidence-check%2Ffile
const res = await pay("https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file");
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.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.aiskills402.com/v1/skills/screenshot-evidence-check/file")
    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
5 min agoPassed402540 ms$0.03
4 h agoPassed40279 ms$0.03
8 h agoPassed402244 ms$0.03
12 h agoPassed402444 ms$0.03
15 h agoPassed4022.0 s$0.03
25 h agoPassed402418 ms$0.03