Score
by dappgrade in Onchain & crypto
dappgrade score — front-end integrity verdict for an onchain app, looked up by contract address. Inspects the app's public web front-end, not contract bytecode or admin control. Returns ok / caution / avoid / unknown with the coverage the verdict rests on.
https://dappgrade.vercel.app/v1/score- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 1.5 s
- 2.1 s slowest 5%
- Last check
- Passed
- 15 min ago, next in 15 min
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://dappgrade.vercel.app/v1/score
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://dappgrade.vercel.app/v1/score?address=0x6cb442acf35158d5eda88fe602221b67b400be3e&chain=8453Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | the contract address the agent is about to call |
chain | string | Yes | EVM chain — id (8453), CAIP-2 (eip155:8453), or name (base, mainnet, arbitrum, optimism) |
Example response
The provider's example. We can't check it without paying.
Example response, 28 lines
{
"coverage": 0.65,
"flags": [],
"freshness": {
"age_seconds": 25140,
"checked_at": "2026-08-17T09:47:12Z",
"stale": false
},
"reasons": [
{
"code": "COVERAGE_BELOW_TARGET",
"detail": "coverage 65% < 80%"
},
{
"code": "TIER_0_ONLY",
"detail": "tier-0 static checks cannot clear a dApp (§2.3)"
},
{
"check": "trust.headers",
"code": "CHECK_FAILED",
"detail": "present: HSTS"
}
],
"score": 87,
"tier": 0,
"verdict": "caution",
"verdict_reason": "coverage 65% < 80%; tier-0 static checks cannot clear a dApp (§2.3)"
}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://dappgrade.vercel.app/v1/score?address=0x6cb442acf35158d5eda88fe602221b67b400be3e&chain=8453'
# 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://dappgrade.vercel.app/v1/score?address=0x6cb442acf35158d5eda88fe602221b67b400be3e&chain=8453' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fdappgrade.vercel.app%2Fv1%2Fscore
const res = await pay("https://dappgrade.vercel.app/v1/score?address=0x6cb442acf35158d5eda88fe602221b67b400be3e&chain=8453");
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://dappgrade.vercel.app/v1/score?address=0x6cb442acf35158d5eda88fe602221b67b400be3e&chain=8453")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 15 min ago | Passed | 402 | 897 ms | $0.01 |
| 6 h ago | Passed | 402 | 1.5 s | $0.01 |
| 11 h ago | Passed | 402 | 860 ms | $0.01 |
| 16 h ago | Passed | 402 | 890 ms | $0.01 |
| 21 h ago | Passed | 402 | 844 ms | $0.01 |
Show 10 older checks
| 26 h ago | Passed | 402 | 1.6 s | $0.01 |
| 31 h ago | Passed | 402 | 1.7 s | $0.01 |
| 36 h ago | Passed | 402 | 876 ms | $0.01 |
| 40 h ago | Passed | 402 | 1.6 s | $0.01 |
| 45 h ago | Passed | 402 | 938 ms | $0.01 |
| 2 days ago | Passed | 402 | 1.5 s | $0.01 |
| 2 days ago | Passed | 402 | 811 ms | $0.01 |
| 2 days ago | Passed | 402 | 1.4 s | $0.01 |
| 3 days ago | Passed | 402 | 1.6 s | $0.01 |
| 3 days ago | Passed | 402 | 1.5 s | $0.01 |