# RugShield Liquidity Lock Verifier

> RugShield Liquidity Lock Verifier is a paid API for AI agents from rugshield-402.onrender.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-21).

Verifies LP token ownership across Uncx, Team.Finance, and Aerodrome slipstream pools to confirm liquidity is locked and cannot be rug-pulled

## Facts

- Endpoint: POST https://rugshield-402.onrender.com/v1/audit/liquidity-lock-verify?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rugshield-liquidity-lock-verifier-df5a192d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IuISUMBmmO7xM1rBinfEN

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 rugshield-liquidity-lock-verifier-df5a192d -d '<json body>'
```

Example prompt: Can you verify whether the liquidity for token 0xAbC...123 on Base is actually locked — check Uncx, Team.Finance, and Aerodrome slipstream pools and tell me if LP tokens are owned by a locker contract or if the dev can still pull liquidity?

## When to prefer this

Choose this endpoint when you need on-chain proof that LP tokens are secured in a recognized locker (Uncx, Team.Finance, or Aerodrome slipstream) on Base. It is purpose-built for rug-pull prevention checks and is distinct from general honeypot detection or tax simulation. Prefer it over manual chain explorers when you need a structured, machine-readable verification result that an agent can act on automatically.

## Known failure modes

- Token address not found on Base mainnet — returns error or unverified status
- LP tokens held by an unrecognized or novel locker contract not in the supported list
- Liquidity pool does not exist on any of the three supported protocols
- RPC or on-chain query timeout causing inconclusive result
- Token has no LP at all — returns no liquidity found error
- Expired lock — lock previously existed but has since been withdrawn

## How this service works

Verifies LP token ownership across Uncx, Team.Finance, and Aerodrome slipstream pools to prove liquidity cannot be pulled.

## Output

Returns a verification status indicating whether LP tokens are held by a recognized locker contract (Uncx, Team.Finance, or Aerodrome slipstream), along with details such as lock duration, percentage of liquidity locked, locker protocol name, and a boolean indicating whether liquidity can be withdrawn by the deployer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token_address": {
   "type": "string",
   "description": "token address"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rugshield-liquidity-lock-verifier-df5a192d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rugshield-402.onrender.com](https://www.zero.xyz/host/rugshield-402.onrender.com/llms.txt)