# Stellar Account Recent Operations Lookup

> Stellar Account Recent Operations Lookup is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Returns the 50 most recent operations executed on a given Stellar account address

## Facts

- Endpoint: POST https://twin.unykorn.org/stellar-operations?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stellar-account-recent-operations-lookup-e7b37b90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ghSdVStdulfs54aLteKhQ

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-account-recent-operations-lookup-e7b37b90 -d '<json body>'
```

Example prompt: Can you pull up the 50 most recent operations on the Stellar account GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN and tell me what's been happening on it?

## When to prefer this

Choose this endpoint when you need a quick, paid, agent-accessible lookup of the most recent 50 operations on any Stellar account without standing up your own Stellar Horizon infrastructure. It is ideal for AI agents that need on-demand Stellar account activity in a single API call with micropayment billing via x402, rather than managing Horizon node connections directly. Best for spot checks, audits, and monitoring of Stellar account activity rather than full historical data exports.

## Known failure modes

- Invalid Stellar account address format (must match ^G[A-Z2-7]{55}$) results in a validation error
- Account not found on the Stellar network returns an empty or error response
- Payment failure via x402 protocol results in no data returned
- Network or Stellar Horizon node unavailability may cause a timeout or 503 error
- Account with no operations returns an empty operations list

## How this service works

The 50 most recent operations on a Stellar account — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok status, a type field set to 'stellar-operations', a list of the 50 most recent operations on the queried Stellar account, a payment receipt including tx_hash, amount paid in USD, and a receipt_id, plus a generated_at ISO8601 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-operations",
  "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-account-recent-operations-lookup-e7b37b90/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)