Picture this. You run a small research group, and you have three drafts nearly ready. One is a clean result, one is a follow-up, and one is a smaller piece you were going to split off from the first. You open arXiv's submission page expecting the usual, and instead you find a new policy: from October 1, every submitter gets "two submissions per calendar month, with a limit of three total active submissions at any given time," across all categories.
So you read the policy, titled Fair Moderation, Equitable Access, and AI: arXiv's Updated Rate Limit Policy. The reasoning is plain. Before AI, there was "an easily discernible, practical limit to the rate at which independent submissions could be produced." Now that limit "is up for debate." arXiv calls the new rule "a stopgap while we determine what may be the new best practice."
The numbers behind it are arXiv's own, and they are stark. In September 2016, the server received 9,869 submissions. In September 2024, it received 20,569. This September it received 40,363, a record, which "generated almost 9,000 support tickets for arXiv staff and moderators." Submissions doubled in two years, and the computer science AI category grew more than six times.
You might wonder whether this is aimed at you. It mostly is not. arXiv's policy allows AI as a disclosed research tool. What moderators are seeing is "thin papers of narrow scope" and "salami" papers split into many submissions, from "a relatively small proportion of authors." That third draft you were planning to carve off is exactly the habit the limit is built to slow down.
What stands out as you read the details is how carefully the limit is drawn. It counts submissions, not announced papers, "because it is submissions that consume moderator time." It applies to the submitter, not to co-authors, so a paper with a long author list does not burn anyone else's allowance. Papers that are held do not count against the next month. A paper you delete before it is announced does not count at all. The unit matches the scarce resource, the exceptions are written down, and the policy says it will be revisited.
Now here is the turn, and it is about the record the APIs.io catalog holds on arXiv itself. The catalog files arXiv as a provider of reading, not writing. Its provider page lists four API pages: the arXiv Query API, the arXiv OAI-PMH API, arXiv Bulk Data and arXiv RSS Feeds. All four are for retrieving the corpus this policy protects. The submission path has no public API on the record, and the agentic access profile is read-only. So if you hoped to script your submissions, the catalog has nothing to point you to.
The scores say the same thing from another angle. The Kin Score is 45.4, in the developing band, with discoverability at 73.2 and contract quality at 58.4, against access clarity at 26.3. The Agent Readiness score is 16.6, agent-aware. Spec presence, agentic access, OpenAPI examples and the rate limit signal are lit on that score. The rate limit signal is the one agent dimension that maps directly to this story, and it is lit for the read side. The catalog does not credit arXiv for the policy you just read, because the policy is written for a human submission form, not for an API.
That gap is the catalog's own finding about its own coverage, and it is worth keeping in mind. The policy itself is the more interesting artifact: a published limit, a unit chosen to match the scarce resource, exceptions spelled out in a FAQ, and a stated intention to revisit. That is what a good API rate limit document looks like, just written for people.
So what do you take away? For your drafts, plan around two a month and three active at once, and think twice before splitting a result into pieces. For the bigger picture, arXiv has rate-limited the input to a scarce human process, and every provider whose agent traffic is outgrowing its reviewers will be writing the same page. When you see one, check the unit, the exceptions and the promise to revisit.
Read the original: https://apis.io/2026/10/19/arxiv-limits-submitters-to-two-papers-a-month-after-submissions-double/