What problem does it solve? Backend and non-browser developers need to call the Wavelength wallet daemon (waved) WalletService correctly, but risk guessing field names from other Lightning implementations like lnd, misusing REST error semantics, or confusing satoshi and millisatoshi amounts. ## Core Features & Use Cases - RPC Reference Navigation: Points to one documentation page per WalletService RPC with request and response field tables, each with a markdown twin for direct fetching. - Transport Selection Guidance: Helps choose gRPC for streaming and typed clients versus REST for simple request-response calls under /v1/wallet/. - Correctness Rules: Enforces documented error shapes, satoshi-denominated integer amounts, and field names from the official docs rather than lnd assumptions. - Use Case: A backend engineer building a payment service connects to waved over gRPC, looks up the exact RPC page for sending a payment, and constructs the request using the documented field table. ## Quick Start Ask the assistant to show how to call a specific WalletService RPC on waved, for example how to connect and send a payment over the REST API.