Contract testing without writing contracts
Your OpenAPI spec says one thing, production does another.
Point your traffic at the proxy and it learns your API’s real contract from observed requests. When a deploy would break that contract, the CI gate blocks it, before your consumers find out.
How it works
Point traffic at the proxy
Send your API traffic through a Cloudflare Worker. It forwards every request untouched and watches the shapes go by. PII is masked at capture, before anything is stored.
It learns the contract
After enough real requests, each endpoint flips from learning to enforcing. The observed shape becomes the contract. No spec files to write or maintain.
The gate blocks breaking deploys
A field disappears or a type changes, and the detector raises a violation. Your pipeline asks the gate before shipping. A breaking change means blocked.
What you get
Breaking-change detection
Removed fields, changed types, and nulls where they do not belong are caught against the enforced baseline.
CI deploy gate
One API call in your pipeline. Pass means ship; blocked means a consumer would break.
Latency regression
When an endpoint’s p50 doubles against its baseline window, it shows up as a warning before users feel it.
PII masking
Emails, tokens, and secrets are masked at capture. The raw values never leave the proxy.
Join the waitlist
We are opening it up gradually. Leave your email and we will write when your turn comes.