# Blockchain.com Explorer API – Solana Transaction Broadcast

> Blockchain.com Explorer API – Solana 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-19).

Broadcasts a signed Solana transaction to the Solana network via the Blockchain.com Explorer API

## Facts

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

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-api-solana-transaction-broadcast-cd3e639e -d '<json body>'
```

Example prompt: Broadcast this signed Solana transaction to the network using the Blockchain.com Explorer API — here's the base64-encoded serialized transaction: 'AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAEDk...'

## When to prefer this

Choose this endpoint when you have an already-signed, base64-encoded Solana transaction ready to submit and want a reliable, paid relay service backed by Blockchain.com's infrastructure. Prefer it over raw RPC node calls when you want a managed API with consistent availability and are operating in an agent-payment (x402) context where micropayments are acceptable.

## Known failure modes

- Transaction already submitted or duplicate — returns error indicating it has already been broadcast
- Malformed or invalid base64 encoding causes a parse error
- Transaction signature invalid or expired — node rejects the transaction
- Network congestion or node unavailability causes a timeout or 5xx error
- Insufficient fee or blockhash expired — transaction rejected by validators
- Payment of $0.005 USDC via x402 fails, resulting in 402 Payment Required response

## How this service works

Paid AI-agent access to Blockchain.com Explorer API

## Output

Returns a response indicating whether the transaction was successfully submitted to the Solana network, typically including the transaction ID or hash that can be used to track confirmation status on a Solana 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-com-explorer-api-solana-transaction-broadcast-cd3e639e/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)
