pikopod status, report, inspect - pikopod

status

pikopod status

Reads /healthz from the running agent and prints the JSON payload: traffic counters, recordings written and dropped, observer panics, alert delivery health, tracked fingerprints, every baseline family with its warmup state, and the spec watcher’s health when armed. Needs pikopod up. Fields are listed under Control plane.

report

pikopod report

The endpoint inventory learned from traffic, from the baselines on disk. Works offline.

examplepay — endpoint inventory (what your app ACTUALLY calls)
  GET    /charges                                       2xx    12 samples  4 fields  [baseline frozen]
  POST   /charges                                       2xx     6 samples  5 fields  [warming up]

Exits 2 with a pointer to pikopod up when no baselines exist yet.

inspect

pikopod inspect [--last 5] [--format json|curl|har]

Stored records per upstream, newest first, with tokenized fields visible so you can verify redaction yourself.

Format	Output
`json`	Pretty-printed records, then a footnote naming what was redacted and the one residual.
`curl`	A `curl` command per record, safe to share.
`har`	A HAR 1.2 document.

# 2026-09-19T10:00:00Z → 201 (84ms)
curl -X POST 'https://api.examplepay.com/charges' \
  -H 'authorization: <<SUBSTITUTE:authorization>>' \
  -H 'content-type: application/json' \
  -d '{"amount":1250,"currency":"NGN"}'

# all values are POST-SANITIZER (tokens/placeholders) — safe to share, not raw traffic

See Inspecting and Redaction.