# Pyfile x402 Nano Block Broadcaster

> Pyfile x402 Nano Block Broadcaster is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Broadcasts a signed Nano cryptocurrency state block to the network via a probe/courier endpoint.

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net/data/nano/courier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pyfile-x402-nano-block-broadcaster-751c8eba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ym9MzygteLY9rupOhtrx2

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 pyfile-x402-nano-block-broadcaster-751c8eba
```

Example prompt: Broadcast this signed Nano state block to the network for me — here's the block data I've already signed.

## When to prefer this

Use this endpoint when you have a pre-signed Nano state block ready and need to broadcast it to the Nano network without running your own node. Ideal for AI agents executing Nano payments or relaying signed transactions as part of automated workflows.

## Known failure modes

- Invalid or malformed block data returns an error response
- Block already processed or duplicate submission may be rejected
- Network node unavailability causes broadcast failure
- Missing or invalid signature causes rejection
- Payment of $0.01 USDC required per call; unpaid requests are rejected with 402

## How this service works

Probe endpoint. POST a signed Nano state block to broadcast it.

## Output

A JSON response confirming whether the signed Nano state block was successfully broadcast to the network, along with any relevant block hash or error details returned by the Nano node.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json",
     "description": "Output payload format."
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pyfile-x402-nano-block-broadcaster-751c8eba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net/llms.txt)