Contract Analysis
by SolSentry in Onchain & crypto
Static risk analysis of a Solana program: upgrade authority, mutability, and the capability flags that matter before you sign anything that invokes it. Answers 'can this program be changed under me, and by whom'.
https://api.solsentry.app/x402/v1/contract-analysis/:solana_address- Price
- n/a
- per call in USDC
- Uptime
- 43.6%
- last 30 days
- Response time
- 388 ms
- 619 ms slowest 5%
- Last check
- Failed
- 5 h ago, next any minute now
Reliability
Latest check failed 5 h 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/contract-analysis/: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/contract-analysis/:solana_addressExample response
The provider's example. We can't check it without paying.
{
"address": "JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4",
"authorities": {},
"explanation": "Upgradeable program. The authority can change the code at any time — only use it if you trust the team.",
"extensions": {},
"fetched_at": 1791403340.2219667,
"flags": [
"UPGRADABLE"
],
"kind": "program",
"known_category": "protocols",
"known_label": "Jupiter Aggregator v6",
"latency_ms": 78.1,
"provenance": {
"as_of_slot": null,
"cached": false,
"fetched_at": "<ISO-8601 UTC>",
"source": null
},
"risk_score": 20,
"verdict": "caution"
}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://api.solsentry.app/x402/v1/contract-analysis/: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/contract-analysis/: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.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%2Fapi.solsentry.app%2Fx402%2Fv1%2Fcontract-analysis%2F%3Asolana_address
const res = await pay("https://api.solsentry.app/x402/v1/contract-analysis/: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.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://api.solsentry.app/x402/v1/contract-analysis/: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 |
|---|---|---|---|---|
| 5 h ago | Expected HTTP 402, got 404 | 404 | 398 ms | - |
| 11 h ago | Expected HTTP 402, got 404 | 404 | 509 ms | - |
| 16 h ago | Expected HTTP 402, got 404 | 404 | 426 ms | - |
| 22 h ago | Expected HTTP 402, got 404 | 404 | 610 ms | - |
| 28 h ago | Expected HTTP 402, got 404 | 404 | 484 ms | - |
Show 10 older checks
| 33 h ago | Expected HTTP 402, got 404 | 404 | 450 ms | - |
| 39 h ago | Expected HTTP 402, got 404 | 404 | 451 ms | - |
| 44 h ago | Expected HTTP 402, got 404 | 404 | 392 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 716 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 521 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 369 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 433 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 1.1 s | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 357 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 345 ms | - |