> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.datafortennis.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.datafortennis.com/_mcp/server.

# Catalogue and player research

Navigate recurring tournaments to editions, draws and matches. A doubles draw is
not a second tournament merely because its discipline differs. Available datasets
describe projected families; release coverage determines their actual presence.

Player match history includes either member of a doubles side exactly once per
match. Restrict the release and filters before comparing counts.

## H2H

Singles H2H uses two player IDs. Doubles H2H uses two exact pairs. Pair member
ordering does not change the matchup, but replacing a partner does. Read excluded,
walkover and retirement result counts separately from ordinary finished results.

## Player-season aggregates

These are precomputed accepted-corpus aggregates, not official complete career or
YTD statistics. Finished known-winner results contribute under the declared
definition. Available serve/return operands determine ratios; missing operands
produce unavailable ratios.

Comparisons require matching metric definitions, release, season, discipline and
coverage. A doubles player's side-level statistics describe the participating
team; do not divide them by two to claim individual contributions.

## Batch points

`POST /v1/points/batch` reads one pinned release for at most 20 match IDs. Its
semantic ceiling is 2,000 points, but your row/byte budget can be lower. Keep the
returned continuation with the same canonical body and ordering. The 100-row
private budget applies across all match wrappers, not per match.