Safety
by svm402-service in Onchain & crypto
Check if a Solana token is safe before buying: rug-pull, scam and honeypot risk with live mint and freeze authority, LP lock status and holder concentration, scored deterministically 0-10. The pre-trade safety screen to run on any unfamiliar token. — $0.01 USDC
https://svm402.com/safety/:address- Price
- n/a
- per call in USDC
- Uptime
- 48.3%
- last 30 days
- Response time
- 196 ms
- 499 ms slowest 5%
- Last check
- Failed
- 4 h ago, next any minute now
Reliability
Latest check failed 4 h ago: Expected HTTP 402, got 410
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://svm402.com/safety/:address
Each call is paid with the request over x402. We can't price the token it asks for: see Payment terms.
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://svm402.com/safety/:addressExample response
The provider's example. We can't check it without paying.
{
"safety": {
"is_honeypot": false,
"risk_score": 25
}
}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://svm402.com/safety/:address'
# 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://svm402.com/safety/:address' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/svm @solana/kit @scure/base
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactSvmScheme } from "@x402/svm/exact/client";
import { createKeyPairSignerFromBytes } from "@solana/kit";
import { base58 } from "@scure/base";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactSvmScheme(client, { signer: await createKeyPairSignerFromBytes(base58.decode(process.env.SVM_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%2Fsvm402.com%2Fsafety%2F%3Aaddress
const res = await pay("https://svm402.com/safety/:address");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,svm]"
import os
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.svm import KeypairSigner
from x402.mechanisms.svm.exact.register import register_exact_svm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_svm_client(client, KeypairSigner.from_base58(os.environ["SVM_PRIVATE_KEY"]))
with x402_requests(client) as session:
res = session.get("https://svm402.com/safety/:address")
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 |
|---|---|---|---|---|
| 4 h ago | Expected HTTP 402, got 410 | 410 | 279 ms | - |
| 9 h ago | Expected HTTP 402, got 410 | 410 | 332 ms | - |
| 14 h ago | Expected HTTP 402, got 410 | 410 | 248 ms | - |
| 19 h ago | Expected HTTP 402, got 410 | 410 | 347 ms | - |
| 23 h ago | Expected HTTP 402, got 410 | 410 | 192 ms | - |
Show 10 older checks
| 28 h ago | Expected HTTP 402, got 410 | 410 | 312 ms | - |
| 33 h ago | Expected HTTP 402, got 410 | 410 | 276 ms | - |
| 37 h ago | Expected HTTP 402, got 410 | 410 | 305 ms | - |
| 42 h ago | Expected HTTP 402, got 410 | 410 | 57 ms | - |
| 47 h ago | Expected HTTP 402, got 410 | 410 | 396 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 300 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 188 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 477 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 195 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 333 ms | - |