phaseo-usage-monitoring
Monitors and debugs Phaseo spend and usage through REST, the phaseo CLI or the Phaseo MCP: credit balance, per-request cost and tokens, log and generation lookup by request ID, analytics by day, model, key or label, 429 rate limits, budgets, alerts and observability destinations. Use when asked why a request cost X or failed, where credits went, to export usage, or about x-request-id, /v1/credits, /v1/analytics, /v1/logs or Retry-After. Not for key restrictions or guardrail setup (phaseo-guardrails), choosing models by price (phaseo-model-selection) or first integration (phaseo-gateway).
- License
- MIT
Pinned to revision ba2f19cc6275, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/phaseo-usage-monitoring/SKILL.md
- skills/phaseo-usage-monitoring/agents/openai.yaml
- skills/phaseo-usage-monitoring/references/alerts-and-destinations.md
- skills/phaseo-usage-monitoring/references/endpoints.md
- skills/phaseo-usage-monitoring/references/mcp-and-cli.md
Every link opens the file at its source, pinned to the revision this page describes.