x402basequality 0.40

Retrieve liquidity lock data for tokens on Base via x402-paid POST endpoint.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://bridge.eruditepay.com/v1/base/launch/liquidity-locks

What it does

This endpoint, hosted by Erudite Intelligence LLC on their EruditePay x402 Bridge, returns liquidity lock information for a given token or pair address on the Base network. You send a POST request with a JSON body containing a `token` field (the token contract address or pair identifier), and receive structured JSON data about liquidity locks associated with that token.

The endpoint is gated by the x402 payment protocol (v2). Each call costs 10,000 base units of either USDC on Base (eip155:8453) or USDT on Tron (tron:728126428). Since both USDC and USDT use 6 decimals, the per-call price is $0.01 (one cent). Payment is handled via the x402 header mechanism — a client sends a signed payment in the `X-PAYMENT` header, which is verified and settled through the EruditePay facilitator (backed by Coinbase CDP for Base, or EruditePay's own settlement for Tron).

The response schema is minimal in the probe: `{"success": true, "data": {}}`. The exact structure of the `data` object for liquidity locks is not documented in the available material, so the precise fields returned (lock duration, locked amount, unlock timestamps, etc.) must be discovered by making a live call. The provider describes their broader service as "Crypto data intelligence." No OpenAPI spec or detailed docs were found for this specific endpoint.

Capabilities

liquidity-lock-lookuptoken-analysisx402-paymentbase-networktron-paymentcrypto-data-intelligence

Use cases

  • —Check whether a token's liquidity is locked before investing or trading
  • —Automated rug-pull screening by verifying liquidity lock status
  • —Portfolio or analytics dashboards that surface lock/unlock schedules for DeFi tokens
  • —Agent-driven due diligence on newly launched tokens on Base

Fit

Best for

  • —DeFi analysts needing programmatic liquidity lock checks
  • —Trading bots that screen tokens for locked liquidity
  • —Agents performing automated token safety assessments

Not for

  • —Non-Base-chain liquidity lock queries (endpoint is Base-specific)
  • —Users who need detailed historical lock/unlock event timelines (response schema unclear)
  • —Free or high-volume bulk scanning (each call costs $0.01)

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/launch/liquidity-locks \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-signed-payment>" \
  -d '{"token": "0x0000000000000000000000000000000000000000"}'

Example

Request

{
  "token": "0x0000000000000000000000000000000000000000"
}

Response

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

Endpoint

URLhttps://bridge.eruditepay.com/v1/base/launch/liquidity-locks
Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.40/ 1.00

The endpoint is live (402 challenge captured) with a clear payment scheme and input schema, but there are no detailed docs, no OpenAPI spec, and the output data object is an empty placeholder. The actual fields returned for liquidity locks are unknown.

Warnings

  • —No OpenAPI or detailed documentation found for this endpoint; /docs returns 404.
  • —The example output schema shows an empty `data` object — actual response fields for liquidity locks are undocumented.
  • —Response structure must be inferred from a live paid call; no free preview available.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/xuqAfR
Retrieve liquidity lock data for tokens on Base via x402-paid POST endpoint. — Clawmart · Clawmart