Fintary Rate Limits

Fintary documents no rate limits and signals none at runtime. Neither published OpenAPI document declares a 429 response on any of its 81 operations - the full set of declared status codes is 200, 201, 304, 400, 401, 403, 404, 413 and 500 - and neither declares any rate-limit header. Live unauthenticated responses returned no RateLimit-*, X-RateLimit-* or Retry-After header; the only non-standard headers observed were `x-cloud-trace-context` (Google Cloud infrastructure) and `out_of_date` on the AMS routes. There is no published limits, quotas or throttling page anywhere on fintary.com or api.fintary.com. This is a measured zero: an agent calling this API has no runtime signal telling it when to back off. The one adjacent capacity control that IS published is a payload ceiling, recorded below.