Holdcheck
by svm402-service in Onchain & crypto
Held-position integrity check — is a token you hold STILL clean? Pass your entry-time liquidity as a baseline. Five tripwires: mint/freeze authority reactivated, honeypot, liquidity collapse (<25% of baseline), risk transformation. Verdict CLEAN / CHEAT_RISK / DEGRADED. Call this on tokens you hold to catch post-buy rug mechanics. — $0.01 USDC
https://svm402.com/holdcheck/:solana_address- Price
- n/a
- per call in USDC
- Uptime
- 72.7%
- last 30 days
- Response time
- 256 ms
- 333 ms slowest 5%
- Last check
- Failed
- 21 h ago, next in 6 h
Reliability
Latest check failed 21 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/:solana_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/:solana_address?liquidity_usd=611119Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
liquidity_usd | string | No | Entry-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/:solana_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/:solana_address?liquidity_usd=611119' \
| 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%2Fholdcheck%2F%3Asolana_address
const res = await pay("https://svm402.com/holdcheck/:solana_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/:solana_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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 21 h ago | Expected HTTP 402, got 410 | 410 | 848 ms | - |
| 30 h ago | Expected HTTP 402, got 410 | 410 | 356 ms | - |
| 40 h ago | Expected HTTP 402, got 410 | 410 | 339 ms | - |
| 2 days ago | Passed | 402 | 268 ms | $0.01 |
| 2 days ago | Passed | 402 | 310 ms | $0.01 |
Show 6 older checks
| 3 days ago | Passed | 402 | 189 ms | $0.01 |
| 3 days ago | Passed | 402 | 159 ms | $0.01 |
| 4 days ago | Passed | 402 | 196 ms | $0.01 |
| 4 days ago | Passed | 402 | 264 ms | $0.01 |
| 4 days ago | Passed | 402 | 333 ms | $0.01 |
| 5 days ago | Passed | 402 | 256 ms | $0.01 |