Changelog
One rate limiter across every surface
API
Rate limiting was unified: MCP calls, REST requests, and Waldo’s own agents running on your behalf all consume from the same per-team limiter, so there is one quota to reason about instead of separate buckets with separate behavior.
Commercial tiers with opportunistic burst capacity sit on top, and teams can check their consumption at the /v1/usage endpoint.
Put Waldo behind your agents
Brand, category, and audience intelligence over 200+ API and MCP endpoints. Sign up, mint a key, and run it against the brands you actually track.