# Blockchain.info ETH Transaction Broadcast

> Blockchain.info ETH 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 Ethereum transaction to the network via the Blockchain.com Explorer API

## Facts

- Endpoint: POST https://api.blockchain.info/explorer-gateway-kt/x402/eth/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-info-eth-transaction-broadcast-4069947a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9-RsCXVUOvRy3K8X_8_Pk

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-info-eth-transaction-broadcast-4069947a -d '<json body>'
```

Example prompt: Submit this signed Ethereum transaction to the Blockchain.com network for me: 0x02f8708201...a3b (the full hex-encoded signed tx) — I need it broadcast to the Ethereum mainnet right now.

## When to prefer this

Use this endpoint when you need to broadcast a pre-signed Ethereum transaction via Blockchain.com's infrastructure. Prefer this over alternatives when your workflow already uses Blockchain.com Explorer data or when you want a single provider for both querying and submitting Ethereum transactions. The $0.005 USDC per-call x402 payment model makes it suitable for agent-driven automated workflows without requiring API key management.

## Known failure modes

- Invalid or malformed hex-encoded transaction returns a 400 error
- Transaction already submitted (duplicate) may return an error or be silently ignored
- Insufficient gas price causes transaction to be rejected by the network
- Network congestion may delay confirmation but broadcast still succeeds
- Payment failure (insufficient USDC balance) results in 402 response before broadcast
- Nonce too low or too high causes transaction rejection

## How this service works

Paid AI-agent access to Blockchain.com Explorer API

## Output

Returns confirmation that the transaction has been submitted to the Ethereum network, typically including the transaction hash that can be used to track the transaction status on a block explorer.

## 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-info-eth-transaction-broadcast-4069947a/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)
