2026-09-25 09:44:45 +08:00
..
2026-09-25 09:44:45 +08:00
2026-09-25 09:44:45 +08:00
2026-09-25 09:44:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-25 01:14:56 +08:00
2026-09-25 09:44:45 +08:00
2026-09-25 02:19:32 +08:00
2026-09-25 02:19:32 +08:00
2026-09-25 02:19:32 +08:00
2026-09-25 02:19:32 +08:00
2026-09-25 05:01:18 +08:00
2026-09-24 01:09:59 +08:00
2026-09-24 18:48:08 +08:00
2026-09-24 17:13:03 +08:00
2026-09-24 17:13:03 +08:00
2026-09-25 09:44:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-24 12:17:45 +08:00
gateway(routing, live): the Gateway view plays what routing does with each request as it happens — the site's Model Routing stage, driven by the gateway's own trace: the agent, magpie with the provider's routing, and its accounts or keys in the order routing weighed them, each saying what it was weighed by (how much is used and when it renews, kept for last, not known yet, resting and until when, left out as its plan doesn't list the model); a request travels to the one put first, one that fails shows what it answered and hands it on, and the story beside it says why the first went first, why each other stands where it does, how long a failed one rests and what said so, and what the agent got; recent requests can be picked to see how each was routed, and the counts are the gateway's since it started. Nothing is worked out again in the page: the gateway records each decision where it makes it. A vendor's Retry-After and rate-limit reset headers now come through with its error, so a rate-limited key or account rests as long as the vendor says rather than a minute
2026-09-25 02:28:32 +08:00
2026-09-24 01:09:59 +08:00
2026-09-25 01:35:24 +08:00
2026-09-25 05:55:33 +08:00