# Kaspa Mempool State

> Kaspa Mempool State is a paid API for AI agents from api.chainmarket-api.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-02).

Returns the live Kaspa mempool state including unconfirmed transaction count, node sync status, and priority feerate

## Facts

- Endpoint: GET https://api.chainmarket-api.workers.dev/api/crypto/kaspa-mempool?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kaspa-mempool-state-7dfa625f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0aZXKPpI02fZn7p1KH2vj

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 kaspa-mempool-state-7dfa625f
```

Example prompt: What does the Kaspa mempool look like right now — how many unconfirmed transactions are queued up, is the node in sync, and what feerate should I use for priority?

## When to prefer this

Use this endpoint when you need the real-time Kaspa mempool snapshot — specifically unconfirmed tx count, node sync status, and feerate — without needing historical time-series data. Prefer this over general blockchain explorers when you need a lightweight, low-cost ($0.002) programmatic check of Kaspa network conditions for fee estimation or congestion monitoring.

## Known failure modes

- Node temporarily out of sync — sync status field will reflect this
- Network hiccup on Cloudflare Worker — may return 5xx
- Mempool data may lag slightly if upstream Kaspa node is catching up
- No historical data available — only current snapshot returned

## How this service works

Live Kaspa mempool state: unconfirmed transaction count, node sync status, priority feerate. Note: History is not exposed by public nodes without external time-series archiving (ARSIV-GEREKLI); returns current 'now' state per ARACLAR.md specification.

## Output

A JSON snapshot of the current Kaspa mempool state including: count of unconfirmed transactions, node synchronization status (boolean or status string), and the priority feerate recommendation. This reflects the live 'now' state with no historical data exposed.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kaspa-mempool-state-7dfa625f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.chainmarket-api.workers.dev](https://www.zero.xyz/host/api.chainmarket-api.workers.dev/llms.txt)