Is the contract machine-readable, and is it kept honest?
A published OpenAPI document that matches the live service, maintained client libraries, and reference documentation a machine can read without executing JavaScript.
Why it separates providers
A spec that has drifted from the service is worse than none. It generates clients that compile and then fail. Documentation that only renders in a browser is invisible to the agents your users increasingly ask instead of reading docs.
The test you can run
Fetch the OpenAPI document, generate a client from it, and call three endpoints. Then fetch the reference page with JavaScript disabled and see whether any of it is there.
What Live Tennis API measures
Not yet measured. This criterion has no published figure. We do not estimate one. The page says so, and the method that will produce it is written down in advance.
What this site does publish, each one measured:
measured October 28, 2026
n=620
measured October 28, 2026
n=620
Check it against us
A free API key takes a minute and needs no card. Every criterion on this site is one you can verify against our live service. The harness runs the same test against any other provider you are evaluating.
The other criteria
| # | Criterion | The question it answers |
|---|---|---|
| 01 | Latency | How quickly does a scoring event reach your code? |
| 02 | Completeness | What share of matches actually carry every point? |
| 03 | Tour coverage | Which tours are in scope, and are they equally served? |
| 04 | Point-by-point | Is there a real per-point record, and does it say where it came from? |
| 05 | Streaming | Can you subscribe instead of poll, and how far does it fan out? |
| 06 | Free tier | Can you evaluate it properly before paying, without a card? |
| 07 | Historical depth | How far back does it go, and what survives at that depth? |