ToolVet
76trust / 100

Payability

by contractlens-api.appin60.com in Other

x402 APIPassing, checked 2 h ago

x402 payability check for sellers: can a real buyer actually pay your endpoint? Sends one payment signed by a fresh unfunded key through your server and facilitator. A payable endpoint fails only on balance; anything else (bad schema, long description, wrong EIP-712 domain, facilitator error) is reported with the exact reason. Base USDC, x402 v1 and v2.

GET
https://contractlens-api.appin60.com/payability
Price
$0.01
per call in USDC
Uptime
94.7%
last 30 days
Response time
540 ms
1.1 s slowest 5%
Last check
Passed
2 h ago, next any minute now

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://contractlens-api.appin60.com/payability

Each call costs $0.01 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

From the listing.

GET https://contractlens-api.appin60.com/payability?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fgas%3FchainId%3D8453

Parameters

ParameterTypeRequiredDescription
urlstringYesFull https URL of your x402 endpoint, with any query params it needs

Example response

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

{
  "firstStatus": 402,
  "reason": "invalid_payload: contract call failed: unable to call contract: execution reverted",
  "status": "payable",
  "url": "https://example.com/api",
  "verdict": "Payable: rejected only for balance.",
  "x402Version": 2
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://contractlens-api.appin60.com/payability?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fgas%3FchainId%3D8453'

# 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://contractlens-api.appin60.com/payability?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fgas%3FchainId%3D8453' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fpayability
const res = await pay("https://contractlens-api.appin60.com/payability?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fgas%3FchainId%3D8453");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://contractlens-api.appin60.com/payability?url=https%3A%2F%2Fcontractlens-api.appin60.com%2Fgas%3FchainId%3D8453")
    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
2 h agoPassed4021.1 s$0.01
7 h agoPassed402573 ms$0.01
11 h agoExpected HTTP 402, got 400400593 ms-
16 h agoPassed402360 ms$0.01
20 h agoPassed402339 ms$0.01
Show 10 older checks
25 h agoPassed402383 ms$0.01
29 h agoPassed402578 ms$0.01
33 h agoPassed402558 ms$0.01
37 h agoPassed402340 ms$0.01
42 h agoPassed402310 ms$0.01
46 h agoPassed402356 ms$0.01
2 days agoPassed402337 ms$0.01
2 days agoPassed402627 ms$0.01
2 days agoPassed402542 ms$0.01
3 days agoPassed402540 ms$0.01