x402basequality 0.72

Pre-transaction security scoring for x402 servers: overall score, risk level, sub-scores, and scam detection for $0.01 USDC.

Price
0.01 USDC / call
Protocol
x402
Verified
no

What it does

The `get_overall_score` endpoint from x402-secure (by t54 Labs) performs a comprehensive security assessment of a given x402 server URL. It returns an overall trust score (0–100), a risk level classification (low/medium/high/critical/unknown), and four sub-scores covering reachability, webpage quality, social sentiment, and on-chain trust. It also flags whether the target is likely a scam and lists specific scam indicators.

The endpoint is designed for autonomous agents that need to validate the safety of an x402-enabled service before committing a payment. You POST a JSON body containing the target URL, and the service evaluates it across multiple dimensions. The output includes server name, scoring details, and a last-updated timestamp. If you don't know which URLs to evaluate, the companion `get_available_resources` endpoint can list valid servers.

The endpoint is live on Base (chain) and costs $0.01 USDC per call via the x402 payment protocol. Payment is made by including a Base64-encoded payment payload in the `X-PAYMENT` header. The maximum timeout is 300 seconds, reflecting that the assessment may involve multiple external checks. x402-secure is open-source and also offers an SDK and proxy for integrating pre-transaction risk assessment into existing x402 workflows.

Capabilities

security-scoringscam-detectionrisk-assessmentx402-server-validationon-chain-trust-scoringsocial-sentiment-analysiswebpage-quality-checkreachability-checkpre-transaction-safety

Use cases

  • Autonomous agents validating an x402 endpoint's trustworthiness before making a payment
  • Wallets or dashboards displaying risk scores for x402 services
  • Automated pipelines filtering out high-risk or scam x402 servers
  • Agent frameworks implementing pre-transaction safety gates

Fit

Best for

  • AI agents making autonomous x402 payments that need pre-transaction safety checks
  • Developers building agent payment workflows who want scam detection
  • Platforms aggregating x402 services and needing trust/risk metadata

Not for

  • General-purpose website security scanning unrelated to x402
  • Real-time transaction monitoring or post-payment fraud detection
  • Endpoints or services not registered in the x402 ecosystem

Quick start

curl -X POST https://x402-secure-api.t54.ai/x402/tools/get_overall_score \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-encoded-payment-payload>" \
  -d '{"url": "https://mesh.heurist.xyz"}'

Example

Request

{
  "url": "https://mesh.heurist.xyz"
}

Response

{
  "url": "https://mesh.heurist.xyz",
  "is_scam": false,
  "risk_level": "low",
  "sub_scores": {
    "reachability": 95,
    "onchain_trust": 80,
    "webpage_quality": 72,
    "social_sentiment": 68
  },
  "server_name": "Heurist Mesh",
  "last_updated": "2025-01-15T12:00:00Z",
  "overall_score": 78,
  "scam_indicators": [],
  "scoring_details": null
}

Endpoint

Transporthttp
Protocolx402
Pay to0x0495d60c927B97d67D5018C6AA65C9b2bebaeED9
CurrencyUSD COIN

Quality

0.72/ 1.00

The endpoint is live (402 challenge captured) with a well-defined outputSchema including input and output fields. However, there are no formal OpenAPI docs, no dedicated documentation page (all /docs, /api, /pricing return 404), and the example response is inferred from the schema rather than observed. Pricing is clear from the challenge.

Warnings

  • No OpenAPI spec or dedicated API documentation available — /docs returns 404
  • Example response is inferred from the outputSchema, not from an actual observed response
  • The 300-second maxTimeoutSeconds suggests calls may be slow depending on the target being assessed

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 19:33:09Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access