# Stellar Asset Supply and Holder Counts

> Stellar Asset Supply and Holder Counts 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 circulating supply and holder count metrics for a specified issued Stellar asset identified by asset code and issuer address.

## Facts

- Endpoint: POST https://twin.unykorn.org/stellar-asset?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-asset-supply-and-holder-counts-669fc63e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fSmalbgh_oVuZw6RXrG7R

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-asset-supply-and-holder-counts-669fc63e -d '<json body>'
```

Example prompt: What's the current circulating supply and number of holders for the Stellar asset with code USDC issued by GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN?

## When to prefer this

Choose this endpoint when you need on-demand supply and holder count data for a specific Stellar-issued asset identified by its code and issuer public key. It is ideal for tokenomics dashboards, due diligence workflows, or monitoring holder growth on the Stellar network. Prefer this over generic blockchain explorers when you need a structured, pay-per-call API response with a built-in receipt for accounting purposes.

## Known failure modes

- Invalid issuer address format (must match G[A-Z2-7]{55}) returns a validation error
- Unknown asset code or issuer combination may return empty/zero results
- Payment failure via x402 protocol results in 402 response before data is returned
- Network timeout if Stellar Horizon node is unreachable
- Missing required params object or fields returns a schema validation error

## How this service works

Supply and holder counts for one issued Stellar asset — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, the asset type label ('stellar-asset'), a generated_at ISO 8601 timestamp, and a receipt object containing the transaction hash, USD amount charged, and a receipt ID. The actual supply and holder count data are embedded in the response payload alongside the receipt.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stellar-asset-supply-and-holder-counts-669fc63e/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)
