The MyTruv CLI is designed to be called by scripts and AI agents, not just humans. Every command returns structured JSON on stdout, keeps human output on stderr, and signals failures with meaningful exit codes.Documentation Index
Fetch the complete documentation index at: https://help.mytruv.com/llms.txt
Use this file to discover all available pages before exploring further.
Output contract
- stdout carries data. JSON by default when piped, or CSV with
--output csv. - stderr carries human-friendly output (colors, tables, warnings) and structured error JSON on failure - ignored by data parsers.
- When run in a TTY, commands render a formatted table on stderr and stdout stays empty. When piped or redirected, stdout is raw JSON.
- Force a specific format with
--json(shorthand for--output json) or-o csv.
Exit codes
| Code | Meaning |
|---|---|
0 | Success |
1 | Error (API error, network error, etc.) |
2 | Authentication required |
Error format
Errors are structured JSON on stderr (never on stdout, so they never pollute parseable output):Examples
Gemini CLI extension
MyTruv CLI ships as a Gemini CLI extension, giving Gemini direct access to your financial data through MCP. Install and authenticate themytruv CLI first (see Overview) so it is on your $PATH, then:
Next steps
CLI Overview
Install, commands, and quickstart
MyTruv MCP
Hosted MCP server (no install)