x402basequality 0.45

Retrieve counterparty addresses for any Tron wallet via pay-per-call x402 endpoint.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://bridge.eruditepay.com/v1/tron/address/counterparties

What it does

This endpoint, operated by Erudite Intelligence LLC, returns counterparty data for a given Tron blockchain address. You POST a JSON body containing a wallet or contract address and receive a JSON response listing the counterparties that address has transacted with. The endpoint is described as "Crypto data intelligence" in its x402 challenge.

Payment is handled via the x402 protocol (HTTP 402 challenge). The endpoint accepts two payment options: USDC on Base (eip155:8453) at 10,000 base units ($0.01) per call, or USDT on Tron (tron:728126428) at 10,000 base units ($0.01) per call. The facilitator for Base payments is Coinbase CDP; Tron payments are handled directly. The provider is FinCEN MSB registered (BSA ID 31000324258137) and operates non-custodially.

Documentation is sparse — the provider's docs endpoint returns a 404, and no OpenAPI spec is published. The request schema is straightforward (a single `address` field), but the response schema is only illustrated with a stub example (`{"success": true, "data": {}}`), so the exact shape of counterparty data returned is not documented. The endpoint is live and responding with a valid x402 v2 challenge.

Capabilities

tron-address-counterpartiesblockchain-analyticscrypto-intelligencex402-paymentpay-per-calltron-networkbase-network-usdcusdt-payment

Use cases

  • —Identify all counterparty addresses a Tron wallet has transacted with for compliance or investigation purposes
  • —Build transaction graphs for Tron addresses in AML/KYT workflows
  • —Enrich on-chain Tron data with counterparty relationships for analytics dashboards
  • —Agent-driven blockchain forensics that need programmatic, pay-per-call access to Tron address data

Fit

Best for

  • —Compliance teams investigating Tron wallet activity
  • —Blockchain analytics agents needing counterparty data on demand
  • —Developers building Tron transaction graph tools

Not for

  • —Non-Tron blockchains (this endpoint is Tron-specific)
  • —Bulk historical transaction export (no evidence of batch support)
  • —Free-tier or unauthenticated usage (payment required on every call)

Quick start

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

Example

Request

{
  "address": "TTikV9JD3xTfk5TDv8HMEvpWmNQS8Fm6Pw"
}

Response

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

Endpoint

URLhttps://bridge.eruditepay.com/v1/tron/address/counterparties
Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live with a valid x402 v2 challenge and a basic input schema, but documentation is effectively absent (docs endpoint 404, no OpenAPI spec). The response example is a stub with an empty data object, so the actual output structure is unknown. Pricing is clear at $0.01/call.

Warnings

  • —No published OpenAPI or detailed API documentation — docs endpoint returns 404
  • —Response schema is only shown as a stub ({"success": true, "data": {}}); actual counterparty data structure is undocumented
  • —The input schema example uses an Ethereum-style zero address (0x000...000) rather than a Tron-format address, which may be a documentation error

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/P76bPg