Rate limits per verified person
A cap on how many submissions one verified person can make in a period. One person with a fast agent can no longer crowd out the applicants who file by hand.
The impact of agents
As AI tools drive the marginal cost of producing a submission toward zero, the volume one person can generate keeps rising. A limit set per request or per session stops catching it. Traditional throttling mechanisms (IP-based rate limits, CAPTCHAs) cannot distinguish between a human who files one high-quality application and an agent that files forty on behalf of the same person.
What must be verified
Government needs submission volume to reflect distinct people rather than agent throughput, so that the count measures genuine demand and not how many an agent filed on one person's behalf.
Protecting access
A cap tuned to the average submitter excludes people with several concurrent eligibility categories, such as multiple disabilities or complex family circumstances. They legitimately file more than most. A threshold set on the population's median denies them the very services their circumstances multiply their need for. The exemption route can also shut users out if proving 'documented circumstances' amounts to a second application on top of the first. Someone who cannot obtain a verified identity at all, for want of the underlying documents or a stable address, is refused the counter itself and denied the service before any cap even applies.
Keeping the path open
- Calibrate caps against real need distributions rather than round numbers.
- Keep the exemption request one step from the quota meter itself.
- Hold open an assisted or in-person identity-verification route, so proving who you are doesn't become the actual barrier.
- Never apply caps to appeals or complaints: rationing redress raises natural-justice concerns no volume argument can answer.
Response surface
A quota is bound to the person rather than to their device or session, with a visible route to an exemption.
The count follows your verified identity, not this device or session. A new browser won’t reset it, and an agent submitting for you draws from the same allowance.
Need more this quarter? A change in circumstances (a move, a new dependent, a lost job) is grounds for an exemption.
The cap manages volume; it never decides a claim. It can never slow the channel that reports wrongful decisions.
Maturity
- Emerging Headline
For the response in production: the NIH per-investigator cap has run since September 2025, explicitly motivated by AI-generated volume.
- Frontier
For identity-bound caps across user-facing services, where threshold calibration and exemption design remain untested.
Precedents
NIH application cap (United States). The National Institutes of Health limits each Principal Investigator to six new, renewal, resubmission, or revision applications per calendar year, across all activity codes except T-series training and R13 conference grants. The policy was explicitly motivated by AI-generated proposals, after NIH observed some investigators submitting more than 40 applications in a single round, and NIH declared that applications 'substantially developed by AI' would not be considered original. The cap reaches about 1.3 percent of applicants.
NIH Grant Support Index, proposed and withdrawn. Before the application cap, NIH proposed an index assigning points to grant types, an R01 counting seven, with a ceiling of 21 points, or three concurrent R01 grants. The rationale was distributional, since a small share of researchers held the bulk of NIH funding. NIH took a different path through the Next Generation Researchers Initiative, so the index never took effect, and it returned to the distributional question with a fresh proposal to cap simultaneous grants per investigator.
What carries over to agent use
The NIH cap is directly transferable to government digital services where per-person submission volume matters: planning objections, freedom-of-information requests, public consultation responses, grant or subsidy applications. The key design variables are:
- Identity binding: Caps require verified identity to prevent circumvention via multiple accounts. Government digital identity infrastructure (e.g. Australia's myGovID, UK's GOV.UK One Login) provides a foundation.
- Threshold calibration: The NIH cap at six per year affects only 1.3% of applicants, preserving access for legitimate heavy users while curtailing outliers. Calibrating thresholds requires empirical analysis of pre-AI submission distributions.
Where things go wrong
A per-human cap is a volume-control mechanism, not an adjudication shortcut. The failure to avoid is throttling the very redress channel that surfaces wrongful decisions, because a cap tight enough to bite on appeals suppresses the evidence that the first decisions were wrong.
Sources
2 references
The instrument, the operating deployment, or the official record itself.