Metrics to track
Pulling data from Reader
Usage history
GET /v1/usage/history returns recent requests with per-row proxyMode, credits, status, and duration. Paginate through and feed into whatever your observability stack is (Datadog, Grafana, a local Postgres, a spreadsheet).
Credits balance
A one-call poll:Instrumenting client calls
Wrap yourreader.read calls in a metrics helper:
Alerts worth having
- Error rate > 5% over a 5-minute window → investigate
- Credit balance < 20% of limit → notify ops
- p95 latency doubles → slowdown or site blocking spike
rate_limitedcount > 10 per minute → need to upgrade or throttle- Webhook
failedDeliveriesrising → your listener is broken
Request ID correlation
Every response (success or error) carries anx-request-id header. Log it on every call. When something goes wrong, include the request ID in your bug report. Reader’s server-side logs key off that ID and we can reconstruct what happened.

