# RuneSwap Rune Minter

> RuneSwap Rune Minter is a paid API for AI agents from runeswap.com, paid per call via x402, $4/call, status unknown (last checked 2026-09-15).

Mints a Bitcoin Rune directly to a specified Bitcoin address on mainnet.

## Facts

- Endpoint: POST https://runeswap.com/api/mint
- Price: $4/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/runeswap-rune-minter-33bd58be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W_Hs3vQdwii324t8hhSeV

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 runeswap-rune-minter-33bd58be -d '<json body>'
```

Example prompt: Mint the rune called UNCOMMON•GOODS to my Bitcoin address bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh using RuneSwap.

## When to prefer this

Use this endpoint when a user wants to mint a specific named Bitcoin Rune directly to their own Bitcoin address on mainnet. Prefer this over alternatives when working within the Bitcoin Runes protocol specifically (not Ethereum ERC-20 tokens or Bitcoin Ordinals inscriptions), and when the user has a specific rune name and a target BTC address ready.

## Known failure modes

- Invalid or non-existent rune name returns an error
- Malformed Bitcoin address causes rejection
- Rune already fully minted or supply exhausted
- Network congestion on Bitcoin mainnet delays or fails the mint
- Payment of $4 USDC not completed or invalid causes rejection
- Bitcoin address format mismatch (e.g. legacy vs segwit) may cause issues

## How this service works

Mint rune on Bitcoin mainnet. Your rune will be minted directly to your Bitcoin address.

## Output

Returns a JSON object with a confirmation message (e.g. 'Your mint request has been sent'), the name of the rune being minted, the destination Bitcoin address, and follow-up instructions telling the user to check their BTC address for the minted rune.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "runeName",
  "btcAddress"
 ],
 "properties": {
  "runeName": {
   "type": "string",
   "description": "The name of the rune to mint"
  },
  "btcAddress": {
   "type": "string",
   "description": "Your Bitcoin address to receive the rune"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "message": {
   "type": "string",
   "example": "Your mint request has been sent",
   "description": "Mint confirmation message"
  },
  "runeName": {
   "type": "string",
   "description": "The name of the rune being minted"
  },
  "btcAddress": {
   "type": "string",
   "description": "The destination Bitcoin address"
  },
  "instruction": {
   "type": "string",
   "example": "Check your btc address for the minted rune",
   "description": "Instructions for the user"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/runeswap-rune-minter-33bd58be/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from runeswap.com](https://www.zero.xyz/host/runeswap.com/llms.txt)