Score
by trustscore.dev in Onchain & crypto
Check if a phone number, crypto token, or property address is trustworthy. Returns a 0-100 trust score, confidence, risk flags, and plain-English summary. Detects phone fraud, spam, robocalls, and VoIP; crypto rugpulls, honeypots, and scam tokens; property deed fraud and shady listings. One call, three asset types.
https://trustscore.dev/api/score- Price
- $0.02
- per call in USDC
- Uptime
- 97.4%
- last 30 days
- Response time
- 352 ms
- 1.2 s slowest 5%
- Last check
- Passed
- 15 min ago, next in 18 min
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://trustscore.dev/api/score
Each call costs $0.02 in USDC on Base, paid with the request over x402.
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.
POST https://trustscore.dev/api/score
content-type: application/json
{
"input": {
"phone_number": "+15551234567"
},
"type": "phone"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
input | object | Yes | |
type | string | Yes | One of: phone. |
Example response
The provider's example. We can't check it without paying.
{
"_meta": {
"latency_ms": 342,
"sources": [
"libphonenumber",
"ipqs"
],
"type": "phone"
},
"confidence": 0.75,
"decision": "safe",
"risk_flags": [],
"score": 97,
"signals": {
"carrier": "T-Mobile",
"e164": "+15551234567",
"is_voip": false,
"valid": true
},
"summary": "This number appears trustworthy with a score of 97/100."
}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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://trustscore.dev/api/score' \
-H 'content-type: application/json' \
--data-raw '{"input":{"phone_number":"+15551234567"},"type":"phone"}'
# 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 - -X POST 'https://trustscore.dev/api/score' \
-H 'content-type: application/json' \
--data-raw '{"input":{"phone_number":"+15551234567"},"type":"phone"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftrustscore.dev%2Fapi%2Fscore&method=POST
const res = await pay("https://trustscore.dev/api/score", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"input": {
"phone_number": "+15551234567"
},
"type": "phone"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://trustscore.dev/api/score",
json={
"input": {
"phone_number": "+15551234567",
},
"type": "phone",
},
)
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 |
|---|---|---|---|---|
| 15 min ago | Passed | 402 | 287 ms | $0.02 |
| 6 h ago | Passed | 402 | 365 ms | $0.02 |
| 11 h ago | Passed | 402 | 296 ms | $0.02 |
| 16 h ago | Passed | 402 | 395 ms | $0.02 |
| 21 h ago | Passed | 402 | 444 ms | $0.02 |
Show 10 older checks
| 26 h ago | Passed | 402 | 268 ms | $0.02 |
| 31 h ago | Passed | 402 | 341 ms | $0.02 |
| 36 h ago | Passed | 402 | 258 ms | $0.02 |
| 40 h ago | Passed | 402 | 331 ms | $0.02 |
| 45 h ago | Passed | 402 | 263 ms | $0.02 |
| 2 days ago | Passed | 402 | 1.1 s | $0.02 |
| 2 days ago | Passed | 402 | 569 ms | $0.02 |
| 2 days ago | Passed | 402 | 1.2 s | $0.02 |
| 3 days ago | Passed | 402 | 763 ms | $0.02 |
| 3 days ago | Passed | 402 | 471 ms | $0.02 |