Holders
by SolSentry in Onchain & crypto
Holder concentration for a mint: holder count, top-1 and top-10 share of supply, and the sampling confidence behind those figures. The confidence field states how the number was obtained, so a partial sample is never presented as a full count.
https://api.solsentry.app/x402/v1/holders/:solana_address- Price
- n/a
- per call in USDC
- Uptime
- 42.5%
- last 30 days
- Response time
- 395 ms
- 753 ms slowest 5%
- Last check
- Failed
- 56 min ago, next any minute now
Reliability
Latest check failed 56 min ago: Expected HTTP 402, got 404
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.solsentry.app/x402/v1/holders/: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
Built from the input schema. Replace the values with your own.
GET https://api.solsentry.app/x402/v1/holders/:solana_addressExample response
The provider's example. We can't check it without paying.
{
"confidence": 0.75,
"count": 5000,
"latency_ms": 2150.7,
"mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"provenance": {
"as_of_slot": null,
"cached": false,
"fetched_at": "<ISO-8601 UTC>",
"source": null
},
"sampled": 5000,
"source": "helius_das",
"supply": 7615117415.90777
}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.007.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.solsentry.app/x402/v1/holders/:solana_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://api.solsentry.app/x402/v1/holders/:solana_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.007 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.007" });
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.007 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.solsentry.app%2Fx402%2Fv1%2Fholders%2F%3Asolana_address
const res = await pay("https://api.solsentry.app/x402/v1/holders/:solana_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.007 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.007"})
register_exact_svm_client(client, KeypairSigner.from_base58(os.environ["SVM_PRIVATE_KEY"]))
with x402_requests(client) as session:
res = session.get("https://api.solsentry.app/x402/v1/holders/:solana_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 |
|---|---|---|---|---|
| 56 min ago | Expected HTTP 402, got 404 | 404 | 644 ms | - |
| 6 h ago | Expected HTTP 402, got 404 | 404 | 390 ms | - |
| 12 h ago | Expected HTTP 402, got 404 | 404 | 820 ms | - |
| 18 h ago | Expected HTTP 402, got 404 | 404 | 634 ms | - |
| 24 h ago | Expected HTTP 402, got 404 | 404 | 820 ms | - |
Show 10 older checks
| 29 h ago | Expected HTTP 402, got 404 | 404 | 427 ms | - |
| 35 h ago | Expected HTTP 402, got 404 | 404 | 440 ms | - |
| 40 h ago | Expected HTTP 402, got 404 | 404 | 425 ms | - |
| 46 h ago | Expected HTTP 402, got 404 | 404 | 520 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 421 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 518 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 388 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 377 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 365 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 439 ms | - |