# Apiosk TX Confirmation Attestation

> Apiosk TX Confirmation Attestation is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Reads a Base blockchain transaction receipt, compares it to the head block, and returns a signed JWS-HS256 attestation with status, block number, and confirmation count.

## Facts

- Endpoint: POST https://gateway.apiosk.com/attestations/tx-confirmation
- 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/apiosk-tx-confirmation-attestation-4d09a726
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GD-UFhLXK2I_Hz2pHfFoj

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 apiosk-tx-confirmation-attestation-4d09a726 -d '<json body>'
```

Example prompt: Can you check whether Base transaction 0xabc123...def got confirmed — I need a signed receipt showing its status, the block it landed in, and how many confirmations it has so far?

## When to prefer this

Choose this endpoint when you need a cryptographically signed, independently verifiable attestation of a Base transaction's status — not just a raw RPC response. Ideal for audit trails, dispute resolution, automated payment pipelines, or any workflow where a tamper-evident receipt is required. Preferable over raw Base RPC calls when you need a structured, signed result that a third party can verify without querying the chain themselves.

## Known failure modes

- Transaction hash not found on Base — returns error indicating tx does not exist
- Transaction still pending with 0 confirmations — returns pending status
- Invalid or malformed transaction hash input
- Network connectivity issues reading Base chain state
- Head block temporarily unavailable causing confirmation count error

## How this service works

Read a transaction receipt on Base, compare it against the head block, and return status (success/failed/pending), the block it landed in and a confirmation count, wrapped in a signed JWS-HS256 receipt. Independently re-checkable from the tx block + head block in the envelope.

## Output

A JWS-HS256 signed envelope containing: transaction status (success/failed/pending), the block number the transaction landed in, confirmation count (head block minus tx block), and the head block reference — allowing independent re-verification from the on-chain data in the envelope.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-tx-confirmation-attestation-4d09a726/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)