Ucla Rate Limits
UCLA publishes no rate-limit documentation of any kind. All 91 operations across its seven contracts run behind a Google Apigee gateway at api.ucla.edu, which is certainly enforcing quota per API Product, but not one contract declares a 429 response and no rate-limit header was observed on any live response. Quota is set when a campus unit approves an application's subscription to an API Product; that decision is not published anywhere. The library IIIF and digital-collections hosts additionally sit behind an Anubis proof-of-work bot challenge, which functions as an undeclared rate limit on automated clients.
Ucla Rate Limits is the machine-readable rate-limit profile for University of California, Los Angeles on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests-per-minute and proof-of-work.
The profile also includes 1 backoff/retry policy defined and response codes documented for throttled.
Tagged areas include Education, Higher Education, University, and Rate Limiting.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/ucla-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.