REST API reference · WCO.ai

Endpoints, authentication with wco_ keys, request and response schemas, rate limit headers, payload ceilings, and every error code the WCO hosted API returns.

The interactive playground and tools require JavaScript because they run the optimization engine locally in your browser rather than sending your data to a server.

WCO.ai — Use fewer tokens, keep the context
Compressor Arena — measured token savings by payload family
Twelve browser-local developer tools
Context audit — measure your own traffic in the browser
Documentation — hosted API, SDKs, and middleware
Pricing — plan limits, overage rates, and cost separation
Methodology — how WCO measures token savings
Evidence registry — every claim and its source
Trust and data handling
Privacy Policy
Terms of Service