# Prove It Onchain > Prove you made it, have it, or said it first, as a one-of-one token on Bitcoin (Counterparty). AI agents can create proofs directly with their own Bitcoin wallet: non-custodial, Bitcoin-native, bring your own wallet. The service fee is one extra output inside the transaction the agent signs, so there is no separate payment step and no account. ## Agent API v1 Base URL: https://proveitonchain.com — JSON in, JSON out, CORS enabled, no API key. Errors are `{"error": "...", "code": "..."}` with a 4xx/5xx status. 1. `GET /api/v1/quote` — current fees. Every product is a flat USD service fee plus the Bitcoin network fee on top. A proof is $2 + network fee (the $2 is returned in sats). 2. `POST /api/v1/proofs` — body `{"claim": "...", "address": "bc1q...", "details"?: "...", "file"?: "", "file_url"?: "https://...", "sha256"?: "<64 hex>", "name"?: "", "fee_rate"?: }`. The server hashes the file (or takes your sha256; the file never has to leave your machine), stores the public claim record at `https://proveitonchain.com/t/.json`, and returns `unsigned_psbt` (base64), `unsigned_tx_hex`, `asset`, `record_id`, `fees`, `expires_at` (30 minutes). The transaction issues the asset with quantity 1, indivisible, locked supply, description = the record URL, and includes the service fee output. 3. Sign every input of `unsigned_psbt` with the key for `address` (SIGHASH_ALL). Do not change any output. 4. `POST /api/v1/broadcast` — body `{"record_id": "...", "signed_psbt": ""}` or `{"record_id": "...", "signed_tx_hex": "..."}`. The server checks it is exactly the composed transaction and pays the exact fee, then relays it and returns `txid`. Relay is open to any address (rate-limited per IP). You can also broadcast the signed hex yourself (e.g. `POST https://mempool.space/api/tx`); the proof is valid either way. 5. `GET /api/v1/proofs/` — `status` is `awaiting_signature`, `expired`, `pending`, or `confirmed`, with `txid`, `asset`, and `verify_url`. Limits: claim ≤ 200 chars, details ≤ 2000, inline files up to about 3 MB (Vercel body limit; use `file_url` up to 6 MB or `sha256` for anything larger). Rate limits per IP: 20 new proofs/hour, 40 broadcasts/hour, 120 reads/minute. Supported addresses: P2WPKH (`bc1q…`) is recommended; the address pays, signs, and receives the token. Coming soon via the API: Inscribe (store the file itself on Bitcoin as an Ordinals inscription, $5 + network fee) and Vanity Names (your own Counterparty name, $21 + network fee). Both are available on the website today. ## Pricing Flat service fee + network fee on top, for every product: - Proof (your own wallet or the API): $2 + network fee - Proof, paid from any Bitcoin wallet (custodial mint at https://proveitonchain.com/pay): $2 + network fee (mint + send miner fees + 330 sats dust) - Inscribe: $5 + network fee - Vanity Name: $21 + network fee (Bitcoin miner fees for registering and delivering your name) ## Links - [Human docs with curl + JavaScript signing example](https://proveitonchain.com/api) - [OpenAPI 3.1 spec](https://proveitonchain.com/openapi.json) - [Verify a proof](https://proveitonchain.com/verify) - [Make a proof on the website](https://proveitonchain.com/inscribe.html) ## What a proof is A proof shows that the issuer published a signed, hashed claim at a point in time. It is not legal title, a certificate of authenticity, or proof of identity. ## Inscription & rune protection Every compose we build for a user-signed transaction (web mint, lock, inscribe payment, POST /api/v1/proofs) only spends UTXOs that an ord indexer confirms hold no inscriptions and no runes. Coins of 546–10,000 sats must be verified directly; unconfirmed coins are accepted only when their parent transaction is verifiably clean. If the indexer is unreachable we return 503 `indexer_unavailable` and build nothing; if clean coins can't cover the cost you get `insufficient_clean_funds` or `no_clean_utxos`. The /api/v1/proofs response includes `utxo_guard` (inputs checked, excluded counts).