# Synapse API — Latest Block (Degen Chain)

> Synapse API — Latest Block (Degen Chain) 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-14).

Fetches the latest block data from the Degen blockchain network via a pay-per-call API.

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/degen/block/latest
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-latest-block-degen-chain-8800f9e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BdiHoslWNOZ-BkoMQYYBx

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-latest-block-degen-chain-8800f9e5 -d '<json body>'
```

Example prompt: What's the latest block on the Degen chain right now? Pull the most recent block data for me.

## When to prefer this

Choose this endpoint when you specifically need the latest block from the Degen blockchain (not Ethereum mainnet or other EVM chains) and want a pay-per-call model via x402 without managing your own RPC node infrastructure.

## Known failure modes

- Network unavailability of the Degen chain RPC node returning empty or error response
- Payment failure via x402 resulting in 402 Payment Required response
- Malformed request body causing 400 Bad Request
- Endpoint timeout if the Degen chain is experiencing congestion or downtime
- Unknown or unsupported chain variant returning an error

## 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 metadata about the latest block on the Degen blockchain network, including block number, block hash, and timestamp. The exact response fields depend on the Synapse API implementation for the Degen chain endpoint.

## 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-latest-block-degen-chain-8800f9e5/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)