What problem does it solve? Investigating the Fianu compliance platform often requires endpoints that no dedicated skill documents — the proxy exposes roughly 900 routes, and guessing URLs or hand-rolling curl calls wastes time and produces errors. This Skill provides the canonical way to reach any route from a shell and to look up its method, path, and auth requirements. ## Core Features & Use Cases - Authenticated API passthrough: The fianu api CLI handles token exchange, /api prefixing, JSON encoding, pagination (--paginate), response filtering (--jq), and non-zero exit codes on errors. - Grep-able route index: references/api-index.md lists all ~900 externally reachable routes with METHOD, PATH, DEST, SERVICE, and AUTH columns, including the PATH-vs-DEST distinction that explains why documented paths sometimes 404. - Write safety guidance: Documents how -f/-F/--input flip the default method to POST, typed field handling, and the rule that the token's subject is always the actor on writes. - Use Case: You need to find why a gate evaluation failed but no skill covers gate routes. Grep the index for gates, check the AUTH column, then call the narrowest GET with --jq to project only the fields you need. ## Quick Start Ask the agent to look up the Fianu API route for a resource like exceptions or attestations and call it with fianu api using pagination and a jq filter.
