# PulseScanner Search

> PulseScanner Search 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-22).

Resolve a search query to a matching PulseChain entity — transaction, block, address, token, validator, slot, or epoch.

## Facts

- Endpoint: GET https://x402.pulsescanner.io/v2/search?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pulsescanner-search-589977b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4yTN1K35EyWAB2fcULe-D

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-search-589977b0
```

Example prompt: Can you look up this PulseChain hash on PulseScanner and tell me what it is — transaction, block, address, or something else? The hash is 0x4f3c8e2a1b7d6f9e0c5a2d8b3e7f1a4c6d9e2b5f.

## When to prefer this

Use this endpoint when you have an unknown string (hash, address, number) from PulseChain (chain ID 369) and need to identify or resolve what on-chain entity it refers to, before calling more specific endpoints for transaction details, token data, or wallet info.

## Known failure modes

- Query does not match any known PulseChain entity — returns empty or null result
- Invalid or malformed query string — may return error or no match
- Network or payment failure — x402 payment of $0.003 USDC required per call
- Entity type filter mismatch — filtering by wrong type returns no results

## How this service works

Resolve a query to a transaction, block, address, token, validator, slot or epoch. PulseChain (chain id 369). $0.003 USDC per call.

## Output

A resolved entity object indicating the matched PulseChain entity type (transaction, block, address, token, validator, slot, or epoch) along with relevant metadata for that entity type.

## 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": {
      "q": {
       "type": "string"
      },
      "type": {
       "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-search-589977b0/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)