42trust / 100

Safety

by svm402-service in Onchain & crypto

x402 APIFailing, checked 4 h ago

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

GET
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

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

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/:address

Example 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 --decode
JavaScript: 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

WhenResultHTTPTimePrice
4 h agoExpected HTTP 402, got 410410279 ms-
9 h agoExpected HTTP 402, got 410410332 ms-
14 h agoExpected HTTP 402, got 410410248 ms-
19 h agoExpected HTTP 402, got 410410347 ms-
23 h agoExpected HTTP 402, got 410410192 ms-
Show 10 older checks
28 h agoExpected HTTP 402, got 410410312 ms-
33 h agoExpected HTTP 402, got 410410276 ms-
37 h agoExpected HTTP 402, got 410410305 ms-
42 h agoExpected HTTP 402, got 41041057 ms-
47 h agoExpected HTTP 402, got 410410396 ms-
2 days agoExpected HTTP 402, got 410410300 ms-
2 days agoExpected HTTP 402, got 410410188 ms-
3 days agoExpected HTTP 402, got 410410477 ms-
3 days agoExpected HTTP 402, got 410410195 ms-
3 days agoExpected HTTP 402, got 410410333 ms-