CLOCK · ELAPSED
19.7%
At this rate you cross the weekly cap before it resets. Ease off, or drop to a lighter model for a while.
usage is tracking the clock almost exactly. · 5.6 days to reset · $467 API-equivalent value this week.
| Fed | Session | Week |
|---|---|---|
| Jul 14 · late | 338 | 93 |
| Jul 14 · 5pm | 322 | 89 |
| Jul 14 · 4pm | 322 | 79 |
| Jul 14 · 3:05pm | 321 | 71 |
| Jul 14 · 6pm | 328 | 92 |
| Jul 14 · 3pm | 316 | 70 |
| Jul 14 · 2pm | 308 | 68 |
| Jul 14 · 10am | 303 | 62 |
| Jul 14 · early | — | 61 |
| Jul 13 · 12:31pm | 289 | 59 |
| Jul 13 · 9:50am | 281 | 58 |
| Jul 13 · instrument | 277 | 57 |
| Jul 13 · early | 272 | 56 |
| Jul 12 · eve3 | 267 | 55 |
| Jul 12 · redesign | 263 | 55 |
| Jul 12 · night2 | 258 | 54 |
| Jul 12 · late night | 254 | 50 |
| Jul 12 · night | 252 | 44 |
| Jul 12 · eve | 231 | 39 |
| Jul 12 · late aft | 229 | 37 |
| Jul 12 · afternoon | 228 | 36 |
| Jul 12 · midday | 220 | 36 |
| 5:30am CT · Jul 12 | 209 | 34 |
| 4:55pm CT · Jul 11 | 198 | 30 |
| 7:28am CT · Jul 11 | 147 | 27 |
| 12:07am CT · Jul 11 | — | 26 |
| ~11:21pm Jul 10 | — | 26 |
| 7:38pm CT · Jul 10 | 115 | 25 |
| 7:28pm CT · Jul 10 | 114 | 24 |
| 7:02pm CT · Jul 10 | 109 | 24 |
| 6:07pm CT · Jul 10 | 102 | 22 |
| 5:48pm CT · Jul 10 | 96 | 21 |
| 5:42pm CT · Jul 10 | 94 | 20 |
| 5:21pm CT · Jul 10 | 93 | 20 |
| 5:19pm CT · Jul 10 | 91 | 20 |
| 4:30pm CT · Jul 10 | — | 19 |
| 3:18pm CT · Jul 10 | 84 | 18 |
| 2:47pm CT · Jul 10 | 70 | 13 |
| 2:43pm CT · Jul 10 | — | 11 |
| 2:27pm CT · Jul 10 | 63 | 9 |
| 2:03pm · Jul 10 | 4 | 8 |
| 10:45am CT · Jul 11 | 157 | 28 |
The headline is an estimate. ccusage reads this machine's API-equivalent spend and calibrates to your last real reading (93% at Jul 14 · late), updating hands-free — no pasting. It sees this machine only, so paste /usage now and then to re-anchor against the true cross-device total. Last ccusage read: ~2:00pm CT Jul 31.