# Avasis Sol-Slot Chain-Tip Clock

> Avasis Sol-Slot Chain-Tip Clock is a paid API for AI agents from agents.avasis.ai, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-31).

Returns the latest Solana chain-tip data—processed slot, confirmed block height, epoch, and slot index—from a single batched PublicNode call, refreshed every second with long-poll and SSE support.

## Facts

- Endpoint: GET https://agents.avasis.ai/v1/tip/sol-slot?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/avasis-sol-slot-chain-tip-clock-822e2ab0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_btgStTEPh1ZQniUwaxw1w

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 avasis-sol-slot-chain-tip-clock-822e2ab0
```

Example prompt: What's the current Solana slot number, confirmed block height, and epoch info right now — and let me know if the data is fresh or stale?

## When to prefer this

Prefer this endpoint when an AI agent or trading bot needs a low-latency, batched, single-call source of Solana chain-tip state (slot, block height, epoch) without managing direct RPC connections. Especially useful for agents that need long-poll semantics to avoid busy-waiting, or that need server-side aggregation of multiple Solana RPC fields into one response. Less suited for historical slot queries or full block data retrieval.

## Known failure modes

- Stale data returned if PublicNode RPC is lagging — indicated by stale:true and elevated ageMs
- Long-poll timeout if no new slot arrives within the wait window — returns last known state
- 402 Payment Required if prepaid meter credit is exhausted — requires topping up at /v1/meter
- Network timeout if agent holds connection longer than server wait limit
- Invalid since parameter returns 400 Bad Request

## How this service works

Solana chain-tip clock for agents that poll: processed slot, confirmed block height, epoch and slot index from one batched PublicNode call, refreshed every 1 s while anyone is polling. Long-poll with ?since=<seq>&wait=25. Prepaid meter price $0.0002/call (packs at /v1/meter); SSE at /v1/stream/tips.

## Output

A JSON object containing: sequence number (seq), epoch, slotIndex, slotsInEpoch, slotProcessed (latest processed slot), blockHeightConfirmed (latest confirmed block height), ageMs (milliseconds since last RPC observation), stale boolean, changed boolean, topic string, and observedAt ISO timestamp. Refreshed every ~1 second server-side; supports long-polling via ?since=<seq>&wait=25 to receive only new data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "seq": 812,
  "data": {
   "epoch": 1071,
   "slotIndex": 230001,
   "slotsInEpoch": 432000,
   "slotProcessed": 462900001,
   "blockHeightConfirmed": 440920000
  },
  "ageMs": 420,
  "stale": false,
  "topic": "sol-slot",
  "changed": true,
  "observedAt": "2026-10-29T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/avasis-sol-slot-chain-tip-clock-822e2ab0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.avasis.ai](https://www.zero.xyz/host/agents.avasis.ai/llms.txt)