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: ELISA providerId: elisa generated: '2026-08-27' method: probed source: >- live unauthenticated requests to https://elisa.tech/wp-json/tribe/events/v1/events and https://elisa.tech/wp-json/ on 2026-08-27, plus a read of every ELISA-published page created: '2026-05-04' modified: '2026-08-27' limit_count: 0 tags: - Embedded - Linux - Linux Foundation - Safety - Rate Limiting description: >- ELISA documents no rate limits for its API surface, and none were observed on live responses. An honest zero. This file REPLACES a 2026-05-04 bulk-sweep scaffold that asserted free/professional/enterprise tiers at 10/100/1000 requests per minute with monthly quotas of 1,000/100,000 and a full set of X-RateLimit-* response headers. ELISA publishes none of that and returns none of those headers. The scaffold was crediting ELISA with a rate-limit posture it does not have. See roadmap#35. headers: {} headers_observed: [] responseCodes: {} limits: [] findings: - probe: GET https://elisa.tech/wp-json/tribe/events/v1/events?per_page=1 status: 200 rate_limit_headers: none note: No X-RateLimit-*, no RateLimit-*, no Retry-After on the response. - probe: GET https://elisa.tech/wp-json/ status: 200 rate_limit_headers: none - source: https://elisa.tech/membership/join/ note: The only published commercial document is the membership dues table; it attaches no API quota or throughput term to any tier. note: >- The absence is consistent with what this surface is — a Linux Foundation project's WordPress REST API, fronted by nginx with New Relic instrumentation. Edge protection almost certainly exists, but it is not documented, not announced in headers, and therefore not something an agent can plan against. NO RateLimits pointer is emitted for this provider. maintainers: - FN: Kin Lane email: info@apievangelist.com