API Rate Limit Tiers Settings Block for React

Edit the constants at the top. PLANS lists the columns in order, lowest first, since that order is what "a higher plan" means. LIMITS lists the rows: each has an id, a name, a one-sentence hint and the largest value its field accepts. SAVED holds what the account has stored when the page opens, one entry for each limit and plan, keyed as "limit:plan". The daily capacity under a plan is worked out from the row whose id is rpm, so keep that row or change capacityLine.

In each row a plan's value must be at least the value of the plan before it; equal is fine. A cell below its neighbour gets a problem line that names the neighbour and its value, and the count in the band's heading ("3 of 4 in order") counts the rows with no such cell. Pressing Apply while any cell is out of order saves nothing: the status line names the first one ("Not applied: Pro is below requests per minute on the plan before it."), the matching tab opens on a phone, and focus goes to that field. Fix it and Apply works again.

It is the requests-per-minute value times 1,440 minutes, written in compact notation with up to three significant digits, so 1,000 a minute reads "About 1.44M requests a day" and 60 reads "About 86.4K". It is the most a key could send at the sustained rate, not a forecast, and it follows every edit. The monthly quota is a separate cap and does not change it.

Everything. Apply keeps the edited limits as the saved ones in this page and says so; nothing is enforced and nothing is sent. To make it real, send the edited limits to your API in the apply handler, check the same ordering rule on the server, and replace the saved copy with what the server returns, showing a failure in the status line. Keep the monotonic check on both sides: a form can be bypassed.

It is a native table with a caption, column headers for the plans and a row header for each limit, so a cell is announced with both. Every field also has its own name ("Burst, Pro"), and its problem line is tied to it as a description. Apply and Discard stay in place and focusable while there is nothing to do: they are marked aria-disabled, and pressing one says so in the status line.

The table would be cramped, so the plans become tabs: Free, Pro and Scale across the top, and the selected plan's four fields below with a hint under each name ("Pro allows 1,000.") that shows the neighbour's value without switching tabs. Problem lines keep their reserved room, so the panel doesn't move when one appears, and the action foot stays at the bottom of the screen while you scroll.