# PulseChain Block by Timestamp

> PulseChain Block by Timestamp is a paid API for AI agents from api.immuta.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Resolves a Unix timestamp to the exact PulseChain block number at or nearest that moment, with optional before/after mode.

## Facts

- Endpoint: GET https://api.immuta.app/pulsechain/block-by-timestamp
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pulsechain-block-by-timestamp-d384bbcc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j_iS2u09DMe0k9z5Y04PP

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 pulsechain-block-by-timestamp-d384bbcc
```

Example prompt: What PulseChain block number was active at Unix timestamp 1700000000? Use 'before' mode so I get the last block at or before that moment.

## When to prefer this

Use this endpoint when you need to anchor a PulseChain blockchain query to a specific point in time — e.g., to replay state, audit historical events, or synchronize off-chain timestamps with on-chain block heights on the PulseChain network specifically.

## Known failure modes

- Missing required 'ts' query parameter returns an error
- Invalid or non-integer timestamp causes a bad request
- Timestamp before PulseChain genesis returns an error or null
- Payment not provided or insufficient results in HTTP 402
- Timestamp far in the future returns an error or nearest known block

## How this service works

Resolve a Unix timestamp to the exact PulseChain block at or nearest that moment.

## Output

Returns the PulseChain block number and its timestamp that corresponds to (or is nearest to) the given Unix timestamp, based on the selected before/after mode.

## 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"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "ts"
     ],
     "properties": {
      "ts": {
       "type": "integer",
       "description": "Unix timestamp in seconds to resolve to a block"
      },
      "mode": {
       "enum": [
        "before",
        "after"
       ],
       "type": "string",
       "description": "'before' = last block at or before ts; 'after' = first block at or after ts"
      }
     }
    }
   },
   "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/pulsechain-block-by-timestamp-d384bbcc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.immuta.app](https://www.zero.xyz/host/api.immuta.app/llms.txt)