# LP Lock Details

> LP Lock Details is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Returns detailed LP lock/burn status for a token, including lock percentages, locker identities, and unlock dates to identify rug-pull risk.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/lp-lock
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lp-lock-details-4260583e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_K90XW2KbGZh8u1gQu9wrw

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 lp-lock-details-4260583e
```

Example prompt: Can you check the full LP lock details for token contract 0x1234...abcd — I want to know how much of the LP supply is locked vs pullable, who the lockers are, and when any locks expire?

## When to prefer this

Use this endpoint when you need granular LP lock data beyond a simple yes/no locked flag — specifically when you need locker identities, exact unlock timestamps, and the breakdown of locked vs burned vs pullable liquidity. Prefer this over summary-level endpoints when assessing rug-pull risk for investment decisions or token due diligence.

## Known failure modes

- Invalid or non-existent token contract address returns an error
- Token has no liquidity pool, resulting in empty or null lock data
- Network issues or RPC failures causing timeout
- Token on unsupported chain returns no data
- Address belongs to a non-LP contract returning unexpected results

## How this service works

Surfaces the LP holders, how much of the LP supply is locked or burned vs pullable, the lockers, and unlock dates. Unlocked liquidity is the clearest rug setup — this shows the detail a one-line 'LP locked: yes/no' hides.

## Output

Returns a breakdown of LP holders and their share of the LP supply, categorized by locked, burned, and pullable amounts, along with locker wallet addresses and the specific dates when each lock expires.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "description": "Token contract address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lp-lock-details-4260583e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)