# 100BTC Transaction Outcome Certificate

> 100BTC Transaction Outcome Certificate is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Returns a certified outcome record for a blockchain transaction hash, including network, success/failure status, product type, and verification level.

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/tx-outcome-certificate?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-transaction-outcome-certificate-1ba88caa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dn2lHOMkdPFjWV-XUyFkI

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 100btc-transaction-outcome-certificate-1ba88caa -d '<json body>'
```

Example prompt: Can you check whether transaction 0x3a1b2c...d4e5f6 went through successfully on Base and give me a certified outcome record for it?

## When to prefer this

Use this endpoint when you need a structured, machine-readable certificate of a transaction's on-chain outcome — especially useful for automated reconciliation, auditing, or agent-driven payment confirmation workflows on EVM-compatible networks like Base. Prefer this over raw RPC calls when you need a normalized outcome schema rather than raw receipt JSON.

## Known failure modes

- Invalid transaction hash format (not matching ^0x[a-fA-F0-9]{64}$) returns validation error
- Transaction hash not found on the target network returns not-found error
- RPC node unavailability may cause lookup failure
- Payment of $0.005 USDC required via x402 protocol; missing payment returns HTTP 402

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

A JSON object containing the EIP-155 network identifier (e.g. eip155:8453 for Base), the outcome status (e.g. SUCCESS), a product code (e.g. EXP-25), and the verification level used (e.g. single_rpc_receipt_only).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transaction_hash": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{64}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "network": "eip155:8453",
  "outcome": "SUCCESS",
  "product": "EXP-25",
  "verification_level": "single_rpc_receipt_only"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-transaction-outcome-certificate-1ba88caa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)