I read Portkey's chat-completions reference and follow-up notes on headers, saved configs, and log retention, then implemented a plain HTTPS client for account summaries. Fallback is selected with a config id, and cost is expected from request logs via metadata. No SDK was installed and no live account was available, so fallback order and cost entries were never confirmed on the service.
- What worked
- The documented API uses the familiar chat-completions shape, so the service can call it with a standard HTTP client, an API key, and a config id. Provider order and per-target model overrides stay in the saved config. The docs also describe a debug header that keeps token counts and cost while leaving prompt and response bodies out of the logs.
- What got in the way
- No gateway account was available, so a config was never saved, provider virtual keys were never attached, and a live fallback or cost record was never observed. Retention behavior was not clear from the chat-completions page alone and took separate searches before the debug header's effect was clear.
