# x402 Chain Intel – Liquidity Lock Check > x402 Chain Intel – Liquidity Lock Check is a paid API for AI agents from x402-chain-intel.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-14). Checks whether the liquidity pool of a token is locked, indicating reduced rug-pull risk for trading bots ## Facts - Endpoint: POST https://x402-chain-intel.vercel.app/api/rug/liquidity-lock - Price: $0.15/call - Payment: x402 - Status: unknown - Last checked: 2026-09-14 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/x402-chain-intel-liquidity-lock-check-84ab728c - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S-shYMGWdgao8iOXuxFI7 Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability x402-chain-intel-liquidity-lock-check-84ab728c -d '' ``` Example prompt: Before my bot buys into this token at 0x1234abcd...5678 on Ethereum, check whether the liquidity pool is locked and tell me the lock duration and which locker protocol is holding it. ## When to prefer this Choose this endpoint when you need a programmatic, per-call liquidity lock signal for trading bot automation or snipe screening, especially when paying only $0.15 USDC per check via the x402 protocol. It is best suited for real-time pre-trade due diligence on specific token contracts rather than bulk historical analytics or social sentiment scoring. ## Known failure modes - Invalid or unrecognized contract address returns an error or empty result - Unsupported chain identifier causes a 400 or 422 error - Token has no associated liquidity pool, resulting in a not-found response - Liquidity lock data not yet indexed for a very recently launched token - Payment failure via x402 protocol (insufficient USDC balance) blocks the request - Rate limiting or network timeout on the vercel deployment returns a 5xx error ## How this service works 27 paid endpoints for trading bots ## Output Returns liquidity lock status for the specified token/pool, including whether the LP tokens are locked, the lock expiry timestamp or duration, the percentage of liquidity that is locked, and the locker protocol (e.g. Unicrypt, Team.Finance, PinkLock) securing the funds — enabling trading bots to programmatically filter out potential rug pulls. ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-chain-intel-liquidity-lock-check-84ab728c/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from x402-chain-intel.vercel.app](https://www.zero.xyz/host/x402-chain-intel.vercel.app/llms.txt)