Movable Ink Rate Limits

Movable Ink publishes no rate limit, quota, burst allowance or 429 contract for the Customer Data API, and the live collector returns no rate-limit signalling headers of any kind. Throughput expectations are set per integration with the Movable Ink Client Experience team, which means an agent or an automated pipeline calling this API has no runtime signal to back off against — it can only observe failures. This is the single most consequential documentation gap on the surface, because every CDP/ESP connector that fans events into the collector (Segment, Tealium, MetaRouter, Braze, Bloomreach, Simon Data) retries on failure.