# WarpPay402 Aerodrome CLAMM Liquidity Manager

> WarpPay402 Aerodrome CLAMM Liquidity Manager is a paid API for AI agents from api.warppay402.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Manage concentrated liquidity positions on Aerodrome Slipstream (CLAMM) — mint, increase, decrease, or collect fees from liquidity positions via an x402-monetized API.

## Facts

- Endpoint: POST https://api.warppay402.com/api/v1/tools/aerodrome-clamm?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/warppay402-aerodrome-clamm-liquidity-manager-061c9447
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tkmyWc9rsLj4lTChbwoFq

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 warppay402-aerodrome-clamm-liquidity-manager-061c9447 -d '<json body>'
```

Example prompt: Mint a new concentrated liquidity position on Aerodrome Slipstream CLAMM for me — use the mint action to open the position.

## When to prefer this

Choose this endpoint when an AI agent needs to programmatically manage concentrated liquidity positions on Aerodrome Slipstream (CLAMM) on Base — especially in automated DeFi workflows that require minting positions, adjusting liquidity, or harvesting fees without a custodial intermediary. Prefer this over generic DEX APIs when working specifically with Aerodrome's CLAMM architecture on Base and when x402 micropayment-per-call billing is acceptable.

## Known failure modes

- Invalid or missing action enum value — returns error if action is not one of mint, increaseLiquidity, decreaseLiquidity, collect
- Payment failure — x402 payment of 0.001 USDC not processed, request rejected with 402
- On-chain transaction failure — blockchain execution error returned in response
- Missing required parameters for the specific action (e.g. position ID for decreaseLiquidity)
- Network or RPC errors on Base blockchain causing timeout

## How this service works

Non-Custodial x402 Monetization Server & MCP Tools for AI Agents.

## Output

Returns a JSON object confirming the action taken, whether it succeeded (success: true/false), and the protocol name (Aerodrome Slipstream CLAMM). May include position ID or transaction details depending on the action performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "action"
 ],
 "properties": {
  "action": {
   "enum": [
    "mint",
    "increaseLiquidity",
    "decreaseLiquidity",
    "collect"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "action": "mint",
  "success": true,
  "protocol": "Aerodrome Slipstream (CLAMM)"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/warppay402-aerodrome-clamm-liquidity-manager-061c9447/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.warppay402.com](https://www.zero.xyz/host/api.warppay402.com/llms.txt)