# Blockchain.com Explorer BCH Transaction Broadcast

> Blockchain.com Explorer BCH Transaction Broadcast is a paid API for AI agents from api.blockchain.info, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-20).

Broadcasts a signed Bitcoin Cash (BCH) transaction to the BCH network via Blockchain.com's Explorer API

## Facts

- Endpoint: POST https://api.blockchain.info/explorer-gateway-kt/x402/bch/broadcast?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchain-com-explorer-bch-transaction-broadcast-92fd1d8f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h7_wUbFPGLpeaRrCSBE_z

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 blockchain-com-explorer-bch-transaction-broadcast-92fd1d8f -d '<json body>'
```

Example prompt: Broadcast this signed Bitcoin Cash transaction to the BCH network: 0100000001abcdef...

## When to prefer this

Choose this endpoint when you need to broadcast a signed Bitcoin Cash (BCH) transaction specifically via Blockchain.com's Explorer API, particularly in agent workflows requiring pay-per-call access via x402 micropayment protocol. Prefer this over generic BCH node RPC calls when you want a managed, reliable relay endpoint without running your own node.

## Known failure modes

- Invalid or malformed hex — returns error if the transaction bytes are not valid BCH serialization
- Double-spend attempt — rejected if inputs are already spent
- Insufficient fee — transaction may be rejected by the network if the fee is too low
- Already broadcast — idempotent resubmission may return an error or no-op depending on node state
- Network unavailability — API may return 5xx if Blockchain.com nodes are unreachable

## How this service works

Paid AI-agent access to Blockchain.com Explorer API

## Output

A broadcast confirmation from the Blockchain.com Explorer API, typically including the transaction ID (txid) if the transaction was successfully accepted and relayed to the Bitcoin Cash network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx": {
   "type": "string",
   "description": "The signed transaction. BTC/BCH: hex-encoded serialized transaction. ETH: hex-encoded signed transaction, 0x prefix optional. SOL: base64-encoded serialized transaction."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchain-com-explorer-bch-transaction-broadcast-92fd1d8f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchain.info](https://www.zero.xyz/host/api.blockchain.info/llms.txt)
