# Stellar Liquidity Pools for Account

> Stellar Liquidity Pools for Account is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-29).

Returns all Stellar liquidity pools in which a given account holds shares

## Facts

- Endpoint: POST https://twin.unykorn.org/stellar-liquidity-pools?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stellar-liquidity-pools-for-account-8fab64fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JNTiawOk6zhqf3oBAg9Z2

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 stellar-liquidity-pools-for-account-8fab64fb -d '<json body>'
```

Example prompt: What liquidity pools does the Stellar account GBVVJJWBMTAYFBSBWLLJ5ZJLZ3PBSIVVRQKLUWWQOQKF2Y5EMZRKSNI have shares in?

## When to prefer this

Use this endpoint when you need to enumerate all liquidity pool positions held by a specific Stellar account address. It is the right choice for DeFi portfolio auditing, rebalancing decisions, counterparty due diligence, or any workflow that requires knowing which AMM pools a Stellar wallet is exposed to. Prefer this over general Stellar account lookups when the specific question is about LP shares rather than balances or transaction history.

## Known failure modes

- Invalid Stellar account address format (must start with G and be 56 characters) returns a validation error
- Account has no liquidity pool positions returns an empty list
- Stellar network unavailable or degraded causes a timeout or service error
- Payment failure via x402 protocol prevents the query from executing
- Malformed request body missing the account field returns a 400-level error

## How this service works

Stellar liquidity pools an account has shares in — Genesis402 / UnyKorn Operator Network

## Output

A JSON response indicating success, the type identifier 'stellar-liquidity-pools', a list of liquidity pools the account participates in with share details, a payment receipt containing a transaction hash, USD amount charged, and a unique receipt ID, plus a generation timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "account": {
     "type": "string",
     "pattern": "^G[A-Z2-7]{55}$"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "stellar-liquidity-pools",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.25,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stellar-liquidity-pools-for-account-8fab64fb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)