x402basequality 0.45

Query TRON token liquidity lock data via x402-paid POST endpoint

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://bridge.eruditepay.com/v1/tron/token/liquidity-lock

What it does

This endpoint, hosted by Erudite Intelligence LLC on their EruditePay x402 Bridge infrastructure, provides liquidity lock information for tokens on the TRON blockchain. You send a POST request with a token address (or symbol) in the JSON body, and receive structured data about that token's liquidity lock status. The endpoint is gated by the x402 payment protocol (version 2), requiring per-call micropayments before data is returned.

Payment can be made in USDC on Base (eip155:8453) or USDT on TRON (tron:728126428), both at 10,000 base units — which equals $0.01 per request (both assets use 6 decimals). The facilitator for Base payments is Coinbase CDP. The provider describes itself as offering "Crypto data intelligence" and is a FinCEN-registered MSB (BSA ID 31000324258137). The Bridge infrastructure supports 20 blockchains and follows the x402 v2.0 open protocol.

Documentation is sparse: the endpoint's schema is available via the x402 challenge's bazaar extension, but there is no dedicated API reference or detailed field-level documentation for the liquidity-lock response. The example output in the schema is a generic `{"success": true, "data": {}}` stub, so the exact shape of the returned liquidity lock data is unknown. The provider's /docs path returns a 404.

Capabilities

tron-token-liquidity-lockcrypto-data-intelligencex402-payment-gatedmulti-chain-paymentmicropayment-per-call

Use cases

  • —Check whether a TRON token's liquidity is locked before investing
  • —Automated due-diligence pipelines that screen TRC20 tokens for rug-pull risk
  • —Dashboard or bot integrations that display liquidity lock status for TRON tokens

Fit

Best for

  • —Agents or bots performing TRON token safety checks
  • —DeFi analytics platforms needing liquidity lock data
  • —Automated token screening workflows

Not for

  • —Querying liquidity locks on non-TRON chains (endpoint is TRON-specific)
  • —Users who need detailed API documentation before integrating (docs are sparse)
  • —Free or unauthenticated access — every call requires an x402 micropayment

Quick start

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

Example

Request

{
  "token": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"
}

Response

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

Endpoint

URLhttps://bridge.eruditepay.com/v1/tron/token/liquidity-lock
Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge captured) with a clear payment scheme and basic input schema via the bazaar extension. However, documentation is effectively absent (all doc paths return 404), the example response is a generic stub with no real field definitions, and the actual shape of the liquidity-lock data is unknown.

Warnings

  • —No dedicated API documentation available — /docs returns 404
  • —Example output in schema is a generic stub; actual response fields are undocumented
  • —Response data shape must be discovered empirically

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/HfJ4qP
Query TRON token liquidity lock data via x402-paid POST endpoint — Clawmart · Clawmart