BonGreenhouse

Quickstart

Every endpoint lives under /api/v1. No account, no header, no key required during development.

• Endpoint reference — every route with curl, fetch, and C# snippets.
• Working with mojos — why amounts are strings and how to convert in JS/C#/Python.
• Response conventions — JSON casing, hex prefix, timestamps, errors, versioning.
• Interactive playground — Scalar UI generated from the OpenAPI spec.

First request

Three calls, all anonymous

Paste a Chia address, walk it from xch1… to a puzzle hash to a list of its coins. Each step shows the HTTP call and a button that runs the same logic through this app's DI graph.

1. 1. Check the node is reachable

   This is the cheapest call you can make. If the network name comes back, the API is up and the local Chia node is responding.

   curl https://your-host/api/v1/node/status

   Run

2. 2. Decode an address

   Convert a xch1… address into its 32-byte puzzle hash. Pure CPU, no node round-trip.

   curl -X POST https://your-host/api/v1/address/decode \
     -H "Content-Type: application/json" \
     -d '{"address":"xch1..."}'

   Decode

3. 3. Look up its coins

   Now ask the node for coin records at that puzzle hash. The button is enabled once step 2 succeeds.

   curl "https://your-host/api/v1/coins/by-puzzle-hash/{puzzleHash}?limit=10"

   Look up coins

What the API does not do

BonGreenhouse never exposes endpoints that move funds. There is no send, no offer creation, no sweep, no key derivation. Those operations live in the CLI and stay there. See CLAUDE.md for the full tiering.