Fleetwide adaptive rate limiting gatekeeper apparatuses, processes and systems

An apparatus, comprising:

• a processor;
• and
• computer memory holding computer program instructions that when executed by the processor improve an operation of a multi-tenant shared computing infrastructure by reducing tenant-level throttle responses from third party rate-limited APIs, the computer program instructions comprising:
• provide a set of accessor usage profiles, at least one accessor usage profile representing legitimate behavior in the multi-tenant shared computing infrastructure by defining a time period, at least one usage constraint, and an accessor type,
• operate upon receipt from an accessor of a request to access a given application in the multi-tenant shared computing infrastructure to select a given accessor usage profile from the set of usage profiles;
• operate upon matching the accessor type to apply the at least one usage constraint in the given accessor usage profile with respect to the defined time period to determine whether the request to access the given application should proceed;
• and
• respond to a determination that permitting the request to access triggers the at least one usage constraint in the given accessor usage profile with respect to the defined time period, to provide the given application a notification.

An apparatus, comprising:

• at least one memory;
• a component collection stored in the at least one memory, the component collection comprising a component collection storage;
• and
• at least one processor disposed in communication with the at least one memory, the at least one processor executing processor-executable instructions from the component collection, the component collection storage structured with processor-executable instructions, comprising:
• obtain, via the at least one processor, an API call permission request datastructure associated with an API call of an application, in which the API call permission request datastructure is structured to identify an API and a set of scopes, wherein the API has an unpublished rate-limit;
• determine, via the at least one processor, a retry-after interval for one or more scopes in the set of scopes, in which existence of a retry-after interval for a given scope indicates that the API previously returned a throttled response for the given scope;
• determine, via the at least one processor, a wait duration associated with the API call, in which the wait duration is determined as a maximum retry-after interval across retry-after intervals that exist for any scope in the set of scopes;
• provide, via the at least one processor, an API call permission response datastructure, in which the API call permission response datastructure is structured to specify the wait duration;
• and
• in response to the wait duration being specified, prevent one or more clients of the API from making API call permission requests until the wait duration has passed.