specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: AspenTech
providerId: aspentech
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Industrial IoT
  - Process Optimization
  - Manufacturing
  - Energy
  - Chemicals
  - Time Series
  - Rate Limiting
description: AspenTech APIs (notably Inmation Web API and Simple Call Interface) run on customer-deployed
  Inmation servers. There are no platform-imposed per-second rate limits; throughput is bounded by the
  customer's deployment topology, server sizing, and tag/process volume. AspenTech does not publish a
  public rate-limit table.
sources:
  - https://www.aspentech.com/
  - https://documentation.inmation.com/
notes: Inmation rate-limits are operator-tunable on the customer's own servers (process engine throttles,
  WebSocket connection limits). No public canonical rate-limit table.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Inmation Web API (deployment-bound)
    scope: server
    metric: varies
    limit: bounded by customer Inmation server sizing and configuration
    notes: Throughput limited by server CPU, tag count, and concurrent WebSocket connections rather
      than a published per-second cap.
policies:
  - name: Operator-Configured
    description: Limits are tuned by the deploying operator on the Inmation core server; no AspenTech
      platform-level public throttle is published.
  - name: Backoff Strategy
    description: Clients should implement exponential backoff with jitter on 429 / 503 from the
      Inmation Web API.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com
    url: https://apievangelist.com