Osano Rate Limits

Osano publishes NO numeric rate limits. Searched the Customer REST API reference, the Unified Consent Core API reference, the developer-docs introduction/versioning/authentication sections and the public FAQ: none states a requests-per-second/minute/hour figure, a burst allowance, a quota, or a per-key/per-account scope. The only rate-limiting signal Osano publishes at all is the HTTP status: 429 "Too Many Requests" is declared on exactly two operations (publishConfig and createRules), returning the same untyped ErrorResponse envelope as every other error. No RateLimit-*, X-RateLimit-* or Retry-After response header is documented anywhere, so an agent cannot see how much budget it has left or how long to wait — it can only observe the failure after the fact. The Introduction does say usage is bounded by contract rather than by a published number: "You are bound by the Osano terms of service and limits placed by those terms." Not probed live: every operation on both APIs requires an API key, so no anonymous response headers are observable.