|
12 | 12 | writes refuse one before sending, and strip any other ``known_of``; |
13 | 13 | - lists are ``{data, has_more, next_cursor}``, continued with ``?cursor=``; |
14 | 14 | - ``Idempotency-Key`` on POST and ``/bulk`` replays the first successful answer for 24 h; |
15 | | -- 429 carries ``Retry-After``; on v2 its only 429 is ``rate_limited``, the failed-PIN |
16 | | - throttle (10 failures lock the key for 15 minutes); under load keel answers 503 ``server_busy`` with |
| 15 | +- 429 carries ``Retry-After``: ``rate_limited`` is the wrong-PIN limit (ten different wrong PINs on |
| 16 | + one key or account within fifteen minutes refuse every PIN there, the right one included, for up |
| 17 | + to 900 seconds; the same wrong PIN never counts twice), ``too_many_requests`` the request budget, |
| 18 | + ``quota_exceeded`` a daily cap; under load keel answers 503 ``server_busy`` with |
17 | 19 | ``Retry-After: 5`` (2026-09-28). |
18 | 20 |
|
19 | 21 | One difference from the TypeScript SDK, on purpose: this client retries 429, 5xx and |
@@ -252,8 +254,9 @@ class RetryPolicy: |
252 | 254 | Idempotency-Key is still running, which is what a retry after a timeout meets: the |
253 | 255 | retry, same key and body, replays its answer once the first has finished. |
254 | 256 |
|
255 | | - Never a 429 with code ``rate_limited``: keel sends it for a wrong PIN, and each retry is |
256 | | - one more failure toward locking the key. keel's 500 is an unhandled exception, almost |
| 257 | + Never a 429 with code ``rate_limited``: keel sends it once ten different wrong PINs have |
| 258 | + been tried on the key or account, and it refuses every PIN there, the right one included, |
| 259 | + for up to fifteen minutes, so a retry inside the run only waits. keel's 500 is an unhandled exception, almost |
257 | 260 | always the same on every try, so it gets one retry, not the full budget. |
258 | 261 |
|
259 | 262 | Waits ``Retry-After`` when the server sends a valid one (whole seconds or an HTTP |
|
0 commit comments