Hookmetry CLI reference
The CLI uses a saved JWT token to list endpoints, forward requests to a local server, and retrieve diagnostics for owned webhook logs.
Commands
| Command | Purpose |
|---|---|
| hookmetry login | Save and verify a CLI token. |
| hookmetry status | Check the saved token and API connection. |
| hookmetry endpoints | List endpoints available to the token. |
| hookmetry listen --endpoint <endpointId> --port <port> | Forward requests to http://localhost:<port>. |
| hookmetry diagnose <logId> | Display validation, forensic, and destination information. |
| hookmetry explain <logId> | Request AI remediation for a failed eligible log. |
Authentication and explain
The CLI stores its token in ~/.hookmetry/config.json. Protect the file as a bearer credential. The diagnose command is account-scoped and can retrieve only logs owned by the token. The explain command returns no analysis for a valid log and is subject to the account plan allowance.
CLI API routes
| Method and path | Purpose |
|---|---|
| GET /api/cli/diagnose/:logId | Return the log summary, validation result, reconstruction report, and destination result. |
| GET /api/cli/explain/:logId | Return cached AI remediation or trigger analysis for an eligible failed log. |