# PulseScanner Recent Blocks

> PulseScanner Recent Blocks is a paid API for AI agents from x402.pulsescanner.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-21).

Returns the most recently indexed blocks on PulseChain (chain ID 369), ordered newest first, with optional pagination.

## Facts

- Endpoint: GET https://x402.pulsescanner.io/v2/blocks?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pulsescanner-recent-blocks-34108f9a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zakTw4VFQBuOBIoNZVSZF

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 pulsescanner-recent-blocks-34108f9a
```

Example prompt: Can you pull the 10 most recent blocks from PulseChain (chain ID 369) for me, newest first?

## When to prefer this

Use this endpoint when you need a paginated feed of the most recent PulseChain blocks in reverse-chronological order. Prefer it over the head-preview-lane endpoint when you want finalized, indexed blocks rather than pre-finalization blocks. Best suited for block explorers, chain monitoring dashboards, or agents that need to track recent on-chain activity on PulseChain specifically.

## Known failure modes

- Invalid cursor token returns 400 or empty result
- Limit parameter out of range returns validation error
- Payment not included or insufficient USDC returns 402 Payment Required
- Network or upstream node unavailability returns 503
- Chain reorganization may cause transient inconsistencies in block ordering

## How this service works

Recent blocks, newest first. PulseChain (chain id 369). $0.003 USDC per call.

## Output

A paginated list of recent PulseChain blocks ordered newest first, each containing block metadata such as block number, hash, timestamp, validator address, transaction count, and gas usage. A cursor is returned for fetching subsequent pages.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "string"
      },
      "cursor": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pulsescanner-recent-blocks-34108f9a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.pulsescanner.io](https://www.zero.xyz/host/x402.pulsescanner.io/llms.txt)