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: Sparx Enterprise Architect
providerId: sparx-enterprise-architect
created: '2026-05-04'
modified: '2026-08-29'
generated: '2026-08-29'
method: searched
source: >-
  https://www.sparxsystems.jp/help/17.0/oslc_am_top.html,
  https://www.sparxsystems.jp/help/17.0/query_capability.html,
  https://www.sparxsystems.jp/en/MCP/
tags:
  - Enterprise Architecture
  - Rate Limiting
description: >-
  Sparx Systems publishes no rate limits, no quota, and no throttling response headers for any of
  its programmatic surfaces, and structurally would not: the Pro Cloud Server OSLC API runs on the
  customer's own infrastructure, and the COM Automation Interface, scripting engine and MCP server
  are in-process on the user's own machine. Throughput is bounded by the customer's hardware and
  database, not by a vendor policy. This replaces a 2026-05-04 scaffold that invented per-tier
  request-per-minute limits, monthly quotas and X-RateLimit-* headers, none of which exist.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
evidence:
  - url: https://www.sparxsystems.jp/help/17.0/oslc_am_top.html
    status: 200
    finding: OSLC Architecture Management 2.0 conformance list contains no throttling or quota requirement.
  - url: https://www.sparxsystems.jp/help/17.0/query_capability.html
    status: 200
    finding: >-
      Query Capability documents oslc.where, oslc.select, oslc.properties and oslc.prefix and no
      paging, page-size or result-cap parameter — the closest thing to a load control on the API,
      and it is absent.
  - url: https://www.sparxsystems.jp/en/MCP/
    status: 200
    finding: >-
      The only published runtime bound on the MCP server is a client-side timeout (-setTimeout,
      3-600 seconds, default 3), which is a wait ceiling rather than a rate limit.
observed_runtime_bounds:
  - name: MCP server communication timeout
    scope: client process
    default_seconds: 3
    configurable_range_seconds: [3, 600]
    note: >-
      Not a rate limit. Recorded here because it is the only published number an agent integrator
      must tune, and it is the one the provider says to raise when the repository sits behind a Pro
      Cloud Server.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com