# Developer Resources & Bitcoin API

> Inspect the QBitcoin technology stack, current health and readiness endpoints, and the boundary between static pages, app UI and the Rust API.

The API provides health checks and read-only Bitcoin mainnet explorer endpoints.

- GET /api/v1/health: HTTP 200 with {"status":"ok"}.
- GET /api/v1/ready: HTTP 200 with {"status":"ready"} when PostgreSQL and Redis respond; otherwise HTTP 503 with {"status":"unavailable"}.

Explorer routes under /api/v1/explorer/ include overview, market (CoinMarketCap quote, CoinLore fallback and Kraken hourly BTC/USD prices), search, blocks/{id}, transactions/{id}, addresses/{id}, and addresses/{id}/transactions. Amounts are decimal satoshi strings; snapshots identify mainnet, source and update time. GET /api/v1/tools documents all 40 contracts. Public calculations accept POST /api/v1/tools/{slug}; network tools reuse the explorer provider layer. Key, seed, message signing and PSBT tools run locally in Rust/WASM. Broadcast accepts only an already signed transaction after explicit review. The wallet page links to working local generators and documents their limits. The stack uses plain HTML/CSS, native JavaScript, Rust/Axum, PostgreSQL and Redis. Secrets and API credentials must remain outside browser-readable configuration.

[Security model](https://qbitcoin.live/security/index.md) · [QBitcoin home](https://qbitcoin.live/index.md)