33trust / 100

Dossier

by SolSentry in Onchain & crypto

x402 APIFailing, checked 5 h ago

Consolidated investigation file for one wallet: identity signals, funding and outflow behaviour, cluster membership, and the tokens attributed to it, assembled into a single report. The heaviest route in the catalog — it aggregates what the cheaper endpoints answer separately.

GET
https://api.solsentry.app/x402/v1/dossier/:solana_address
Price
n/a
per call in USDC
Uptime
43.6%
last 30 days
Response time
389 ms
686 ms slowest 5%
Last check
Failed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

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/dossier/: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/dossier/:solana_address

Example response

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

{
  "built_at": "<ISO-8601 UTC>",
  "provenance": {
    "as_of_slot": null,
    "cached": false,
    "fetched_at": "<ISO-8601 UTC>",
    "source": null
  },
  "wallet": "<base58 wallet>"
}

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.5.

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/dossier/: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/dossier/:solana_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.5 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.5" });
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.5 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.solsentry.app%2Fx402%2Fv1%2Fdossier%2F%3Asolana_address
const res = await pay("https://api.solsentry.app/x402/v1/dossier/: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.5 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.5"})
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/dossier/: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

WhenResultHTTPTimePrice
5 h agoExpected HTTP 402, got 404404399 ms-
11 h agoExpected HTTP 402, got 404404501 ms-
17 h agoExpected HTTP 402, got 404404453 ms-
22 h agoExpected HTTP 402, got 404404388 ms-
28 h agoExpected HTTP 402, got 404404867 ms-
Show 10 older checks
34 h agoExpected HTTP 402, got 404404448 ms-
39 h agoExpected HTTP 402, got 404404417 ms-
45 h agoExpected HTTP 402, got 404404473 ms-
2 days agoExpected HTTP 402, got 404404484 ms-
2 days agoExpected HTTP 402, got 404404405 ms-
3 days agoExpected HTTP 402, got 404404396 ms-
3 days agoExpected HTTP 402, got 404404379 ms-
3 days agoExpected HTTP 402, got 404404117 ms-
3 days agoExpected HTTP 402, got 404404363 ms-
3 days agoExpected HTTP 402, got 404404365 ms-