x402basequality 0.45

Audit TRON tokens via x402 micropayment — returns security and risk data for any token address.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint performs a token audit on the TRON blockchain. You POST a JSON body containing a token address (or symbol), pay per-call via the x402 protocol, and receive structured audit/risk data in return. The endpoint is operated by Erudite Intelligence LLC and is part of their broader crypto data intelligence suite hosted on the EruditePay Bridge.

Payment is accepted in two ways: USDC on Base (eip155:8453) or USDT on TRON (tron:728126428), both at 0.01 USD per call (10,000 base units with 6 decimals). The x402 v2 challenge is live and returns a well-formed 402 response. Settlement is facilitated through the EruditePay Bridge, which supports 20 blockchains and charges 0.5% per settlement on top of the endpoint price.

Documentation is sparse — the example output schema only shows `{"success": true, "data": {}}` with no detail on what fields the audit actually returns. There is no OpenAPI spec, and the linked docs site (`docs.eruditepay.com`) was not reachable during crawl. The endpoint is live and the payment challenge is correctly formed, but without richer documentation or a sample response, the exact audit capabilities remain unclear.

Capabilities

tron-token-auditx402-paymentusdc-baseusdt-troncrypto-risk-analysistoken-security-check

Use cases

  • Audit a TRON token before investing or listing it on an exchange
  • Integrate automated token risk checks into a DeFi aggregator or wallet
  • Screen newly launched TRON tokens for rug-pull indicators
  • Build compliance workflows that flag risky tokens before processing transactions

Fit

Best for

  • Developers building TRON-focused DeFi tools that need per-call token audits
  • Agents or bots that need programmatic, pay-per-use token risk scoring
  • Teams wanting x402-native crypto intelligence without API key management

Not for

  • Auditing tokens on non-TRON chains (separate endpoints exist for other networks)
  • Deep manual smart-contract audits requiring human review
  • Users who need detailed documentation before integrating — response schema is currently undocumented

Quick start

curl -X POST https://bridge.eruditepay.com/v1/tron/launch/token-audit \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"token": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"}'

Example

Request

{
  "token": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"
}

Response

{
  "data": {},
  "success": true
}

Endpoint

Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live with a valid x402 v2 challenge and clear pricing, but the response schema is essentially empty (just `{"success": true, "data": {}}`), there is no OpenAPI spec, and the docs site returned nothing. The actual audit data fields are unknown, making it hard for agents to consume the output reliably.

Warnings

  • Response schema is undocumented — the example output only shows an empty data object
  • docs.eruditepay.com was not reachable during crawl; no external documentation available
  • Exact audit fields (risk scores, contract flags, etc.) are unknown and must be discovered empirically

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:17:40Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access