Query liquidity lock data for any token on Base via x402-paid endpoint.
What it does
This x402-gated endpoint from Erudite Intelligence LLC returns liquidity lock information for a given token address on the Base network. You POST a JSON body containing a `token` field (an on-chain address or symbol), and the endpoint responds with structured JSON data about that token's liquidity lock status.
Payment is required per-call via the x402 protocol. The endpoint accepts two payment options: USDC on Base (eip155:8453) or USDT on Tron, both at 10,000 base units — which equals $0.01 per request (both USDC and USDT use 6 decimals). Payment is facilitated through the EruditePay Bridge, which supports settlement via Coinbase CDP on Base and direct settlement on Tron. The provider describes the endpoint's category as "Crypto data intelligence."
Documentation is sparse. The response schema shows `{"success": true, "data": {}}` as an example but does not detail the fields within `data`. There is no OpenAPI spec, and the provider's /docs path returns a 404. The endpoint is live and returning a valid x402 v2 challenge. The provider, Erudite Intelligence LLC, operates the EruditePay x402 Bridge facilitator and is listed as a FinCEN MSB (BSA ID 31000324258137).
Capabilities
Use cases
- —Check whether a token's liquidity pool is locked before investing
- —Automated due diligence on new Base token launches
- —Build dashboards that surface liquidity lock status for DeFi tokens
- —Agent-driven portfolio risk assessment incorporating LP lock data
Fit
Best for
- —DeFi analysts needing programmatic liquidity lock lookups
- —Trading bots that screen tokens for locked liquidity
- —AI agents performing on-chain token safety checks
Not for
- —Non-crypto or non-DeFi use cases
- —Users who need detailed historical liquidity analytics (response schema unclear)
- —Free-tier or no-crypto-wallet callers (x402 payment required)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/liquidity-lock \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'Example
Request
{
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live with a valid x402 v2 challenge and includes a basic Bazaar schema, but the response payload is essentially undocumented (example data is an empty object). No OpenAPI spec or detailed docs are available, so the actual fields returned are unknown.
Warnings
- —Response schema is undocumented — the example output shows an empty 'data' object with no field definitions.
- —No OpenAPI specification or dedicated documentation page found (provider /docs returns 404).
- —The exact contents and structure of the liquidity lock response must be discovered empirically.
Citations
- —Endpoint returns x402 v2 challenge with USDC on Base (amount 10000) and USDT on Tron (amount 10000)https://bridge.eruditepay.com/v1/base/token/liquidity-lock
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and charges 0.5% per settlementhttps://bridge.eruditepay.com
- —USDC and USDT use 6 decimals, so 10000 base units = $0.01https://bridge.eruditepay.com