# Synapse API — Sonic Latest Block

> Synapse API — Sonic Latest Block is a paid API for AI agents from synapse-api-brown.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Fetches the latest block data from the Sonic blockchain network

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/sonic/block/latest
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-sonic-latest-block-1a7d48bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RmwwjR5kRzFEtcWFGn77C

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 synapse-api-sonic-latest-block-1a7d48bb -d '<json body>'
```

Example prompt: What is the latest block on the Sonic blockchain right now? I need the current block number and timestamp.

## When to prefer this

Choose this endpoint when you specifically need the latest block data from the Sonic blockchain network and are comfortable with pay-per-call micropayment via x402. Prefer this over self-hosted RPC calls when you lack direct Sonic node access or want a managed, low-setup solution for occasional block queries.

## Known failure modes

- Network or RPC node unavailability returns an error response
- Payment failure (insufficient USDC balance) results in 402 response before processing
- Malformed request body returns validation error
- Temporary Sonic network issues may return stale or error data
- Rate limiting may occur under high request volume

## How this service works

High-speed API suite for AI processing, web scraping, and smart data utilities across 57+ blockchain networks. Pay-per-call via x402.

## Output

Returns the latest block data from the Sonic blockchain network, including block number (height), block hash, timestamp, and potentially other block-level metadata such as transaction count and parent hash.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "properties": {},
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synapse-api-sonic-latest-block-1a7d48bb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from synapse-api-brown.vercel.app](https://www.zero.xyz/host/synapse-api-brown.vercel.app/llms.txt)