# Recent Bitcoin Transactions for an Address

> Recent Bitcoin Transactions for an Address is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.006/call, status unknown (last checked 2026-10-01).

Fetches the most recent Bitcoin transactions for a given BTC address

## Facts

- Endpoint: POST https://twin.unykorn.org/btc-address-txs?utm_source=zero.xyz
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recent-bitcoin-transactions-for-an-address-7341a67b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nzvgzGq9o5JqjlSO6D59X

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 recent-bitcoin-transactions-for-an-address-7341a67b -d '<json body>'
```

Example prompt: Can you pull up the recent Bitcoin transactions for the address 1A1zP1eP5QGefi2DMPTfTL5SLmv7Divfna so I can see what activity has been happening on it?

## When to prefer this

Choose this endpoint when you need quick, on-demand lookup of recent Bitcoin transaction history for a specific address and are operating in an x402-enabled agentic payment context. Prefer it over public block explorer APIs when you need a single paid, metered call with receipt-level auditability rather than managing API keys. It is especially useful for agents that need to verify payment receipt, audit wallet activity, or monitor a known BTC address as part of a larger workflow.

## Known failure modes

- Invalid or malformed Bitcoin address returns an error
- Address with no transaction history may return an empty transaction list
- Network or node connectivity issues may cause timeouts
- Payment failure over x402 protocol results in no data returned
- Rate limiting if too many requests are made in quick succession

## How this service works

Recent Bitcoin transactions for an address — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object confirming success, the type of data returned (btc-address-txs), a payment receipt with transaction hash, USD amount, and receipt ID, plus a generated_at ISO8601 timestamp. The actual transaction records for the queried Bitcoin address are included in the response payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "address": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "btc-address-txs",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.006,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recent-bitcoin-transactions-for-an-address-7341a67b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)