47trust / 100

Holdcheck

by svm402-service in Onchain & crypto

x402 APIFailing, checked 2 h ago

Is a Solana token I already hold still safe? Post-buy rug-pull watch for a token I hold: pass your entry-time liquidity as the baseline and the service re-runs the scam screen — mint/freeze authority reactivated, honeypot, liquidity collapse versus baseline, risk transformation — returning CLEAN / CHEAT_RISK / DEGRADED. — $0.01 USDC

GET
https://svm402.com/holdcheck/:address
Price
n/a
per call in USDC
Uptime
70.0%
last 30 days
Response time
236 ms
396 ms slowest 5%
Last check
Failed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 2 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/holdcheck/: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

From the listing.

GET https://svm402.com/holdcheck/:address?liquidity_usd=611119

Parameters

ParameterTypeRequiredDescription
liquidity_usdstringNoEntry-time liquidity baseline (optional)

Example response

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

{
  "address": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263",
  "checked_at": "2026-09-07T12:00:00+00:00",
  "tripwires": [
    {
      "detail": "mint authority revoked",
      "name": "mint_reactivated",
      "tripped": false
    },
    {
      "detail": "liquidity $500,000 vs baseline $611,119",
      "name": "lp_collapsed",
      "tripped": false
    }
  ],
  "verdict": "CLEAN"
}

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/holdcheck/:address?liquidity_usd=611119'

# 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/holdcheck/:address?liquidity_usd=611119' \
  | 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%2Fholdcheck%2F%3Aaddress
const res = await pay("https://svm402.com/holdcheck/:address?liquidity_usd=611119");
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/holdcheck/:address?liquidity_usd=611119")
    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 agoExpected HTTP 402, got 410410335 ms-
7 h agoExpected HTTP 402, got 410410412 ms-
12 h agoExpected HTTP 402, got 410410273 ms-
17 h agoExpected HTTP 402, got 410410141 ms-
21 h agoExpected HTTP 402, got 410410330 ms-
Show 10 older checks
26 h agoExpected HTTP 402, got 410410446 ms-
31 h agoExpected HTTP 402, got 410410332 ms-
35 h agoExpected HTTP 402, got 410410157 ms-
39 h agoExpected HTTP 402, got 410410174 ms-
43 h agoPassed402336 ms$0.01
47 h agoPassed402183 ms$0.01
2 days agoPassed402323 ms$0.01
2 days agoPassed402247 ms$0.01
2 days agoPassed402253 ms$0.01
3 days agoPassed402154 ms$0.01