x402basequality 0.55

Analyze webpage trustworthiness with AI-powered screenshots, security checks, and phishing detection for $0.01 USDC.

Price
0.01 USDC / call
Protocol
x402
Verified
no

What it does

The `get_webpage_trust` endpoint from t54 Labs' x402-secure platform performs AI-powered webpage quality analysis. Given a URL, it returns a trust score, automated screenshot, security assessment, and risk indicators designed for scam and phishing prevention. The service is accessed via the x402 payment protocol on the Base network, costing $0.01 USDC (maxAmountRequired: 10000 in USDC's 6-decimal representation) per request.

The endpoint accepts a POST request with a JSON body containing a single required field: `url` — the webpage to analyze. The response includes the analyzed URL, a server name, status, a webpage analysis object, a screenshot URL, structured result data, and a last-validated timestamp. The maximum timeout is 300 seconds, reflecting the time needed for screenshot capture and AI analysis.

The service is part of the broader x402-secure ecosystem built by t54 Labs, which provides an open-source SDK and proxy adding security layers to x402 agent payments. The platform supports both Base and Solana chains and includes a risk engine called Trustline. No OpenAPI spec or dedicated documentation page was found for this specific endpoint; the schema details come entirely from the x402 challenge's `outputSchema` field.

Capabilities

webpage-trust-scoringautomated-screenshotphishing-detectionsecurity-assessmentscam-preventionrisk-indicatorsx402-paymentbase-networkusdc-payment

Use cases

  • AI agents verifying a merchant website's legitimacy before making a purchase
  • Automated pipelines screening URLs for phishing or scam indicators
  • Security tools generating visual evidence (screenshots) and trust reports for suspicious links
  • Agent workflows that need pre-transaction risk assessment of unfamiliar web services
  • Browser extensions or bots that flag low-trust pages for human review

Fit

Best for

  • AI agents that autonomously browse and transact on the web
  • Fraud prevention workflows needing automated webpage trust scoring
  • Developers building scam-detection features into agent pipelines

Not for

  • Bulk scanning of millions of URLs (300s timeout per request)
  • Replacing full penetration testing or vulnerability scanning tools
  • Use cases requiring free or non-crypto payment methods

Quick start

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

Example

Request

{
  "url": "https://example.com"
}

Response

{
  "url": "https://example.com",
  "status": "completed",
  "result_data": {
    "ssl_valid": true,
    "domain_age_days": 9500,
    "phishing_detected": false
  },
  "server_name": "example.com",
  "last_validated": "2025-01-15T12:00:00Z",
  "screenshot_url": "https://x402-secure-api.t54.ai/screenshots/abc123.png",
  "webpage_analysis": {
    "indicators": [
      "valid_ssl",
      "known_domain",
      "no_phishing_signals"
    ],
    "risk_level": "low",
    "trust_score": 85
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x0495d60c927B97d67D5018C6AA65C9b2bebaeED9
CurrencyUSD COIN

Quality

0.55/ 1.00

The x402 challenge is live and provides a clear input/output schema, pricing, and description. However, there is no OpenAPI spec, no dedicated docs page, and the response schema uses loose type annotations (e.g., 'object|null') without detailed field definitions. The example response is inferred from the outputSchema field names and types, not from actual documentation or sample responses.

Warnings

  • No OpenAPI specification or dedicated API documentation found — /docs, /api, /pricing, /README all return 404.
  • Response schema fields like 'webpage_analysis' and 'result_data' are typed as 'object|null' with no sub-field documentation; the example response is inferred, not sourced.
  • 300-second max timeout suggests potentially slow processing; callers should handle long waits.

Citations

Provenance

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

Agent access