Shell loops stop at a budget refusal, and the call budgets match the API's

shared/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

shared/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

shared/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/audit-discoverability/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/audit-discoverability/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/audit-discoverability/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/design-widgets/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/design-widgets/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/design-widgets/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/find-opening/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/find-opening/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/find-opening/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/optimize-listing/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/optimize-listing/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/optimize-listing/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/plugin-stack/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/plugin-stack/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/plugin-stack/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/submit-plugin/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/submit-plugin/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/submit-plugin/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/track-launch/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/track-launch/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/track-launch/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.

skills/watch-competitors/references/api.md

@@ -24,4 +24,4 @@ A ref fills `{store}/{id}`: `chatgpt:kiwi-com` is `/listings/chatgpt/kiwi-com`.
 
 Answers are always the whole JSON, about ten times the size of the rows a list needs, so keep `limit` small.
 
-A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.
+A cut returns 200. Not found is 404, budget spent is 429 and busy is 503. A shell loop has to check for 429 after each call and `break`, because `curl` exits 0 on it. The `x-openapps-budget` header says what's left: `calls-hour=264, calls-day=894, rows-day=4470`.

skills/watch-competitors/references/cli.md

@@ -24,4 +24,4 @@ A wrong field name prints the allowed ones. When stderr says `truncated`, or a s
 
 ## Exit codes
 
-A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4.
+A cut exits 0. Busy is 1 with "temporarily unavailable", not found is 3 with `Closest:` candidates, and budget spent is 4. A shell loop has to check for 4 after each call and `break`, because the shell carries on past a failed command.

skills/watch-competitors/references/data.md

@@ -28,7 +28,7 @@ Budgets are per IP when signed out, and shared with the website, which holds bac
 | Countries | US | All | All |
 | Combining tags in `listings_list` | Refused | Within one group: capability tags, or job, brand and audience tags | Any |
 | Several apps at once | Refused | Refused | `apps`: 10 on `listings_ranks_history`, 5 on `listings_get` |
-| Calls per hour, 24 hours | 300, 1,000 | 1,000, 5,000 | 5,000, 25,000 |
+| Calls per hour, 24 hours | 1,000, 5,000 | 3,000, 15,000 | 5,000, 25,000 |
 | Rows per 24 hours | 5,000 | 25,000 | 250,000 |
 
 Each answer's `meta.tier` is the plan it was read at: `out`, `free` or `plus`, which is Pro. Keep `limit` small: a run that spends the rows locks the user out of the site too. Make the reads a step names, one at a time or in a short loop that stops at the first refusal. Don't write your own client with retries: it hides refusals and keeps spending.