Add Live Tennis API integration

[bensynapse]

Adds the Live Tennis API integration page — live tennis scores, matches, players, head-to-heads, the 1968-2022 results archive, rankings and in-play statistics as Haystack Documents for RAG and agent pipelines (ATP, WTA, Challenger, ITF and juniors).

• Package: livetennisapi-haystack 0.2.0 on PyPI (published, trusted-publishing/OIDC)
• Repo: https://github.com/livetennisapi/livetennisapi-haystack — CI (tests py3.10-3.13 + lint) green, 81 tests, MIT
• Six components, each returning Documents with a readable content summary and structured meta: LiveTennisMatchFetcher, LiveTennisPlayerSearch, LiveTennisH2HFetcher, LiveTennisArchiveFetcher, LiveTennisRankingsFetcher, LiveTennisMatchStatisticsFetcher; all follow the Haystack secret-management conventions (Secret.from_env_var)
• Tier walls, daily-quota 429s and ambiguous player names surface as readable, meta-tagged Documents an agent can act on instead of tracebacks
• Users bring their own free API key (100 req/day, no card): https://livetennisapi.com/subscribe/free

[vercel]

Someone is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[kacperlukawski]

Thank you, @bensynapse Could you please help me understand if that package was created based on an actual need of a user? I would like to determine if that is something useful for a broader audience.

[bensynapse]

Thanks for asking directly, @kacperlukawski — honest answer:

No, it did not come from an inbound Haystack user request. I'm the developer of the Live Tennis API itself, and this is a vendor-authored integration: I built it so Haystack pipelines can pull live tennis data (scores, players, fixtures, win-probability) without hand-rolling an HTTP component, and I submitted it as part of making the API usable across the agent/RAG ecosystem (we ship the same capability as an MCP server and integrations for several other frameworks).

So the demand signal today is "the API has users; none of them have specifically asked for Haystack" — I'd rather say that plainly than imply otherwise. The concrete audience I had in mind is sports-media and betting-analytics teams building QA/agent pipelines over live sports data, where the fetcher plus a well-typed document shape is the fiddly part this package does once.

If the bar for the integrations page is demonstrated end-user need, I completely understand holding this until someone asks for it — happy to leave the package published on PyPI and revisit, or adjust scope if a leaner example-based listing fits better.

[bensynapse]

Updated the page for livetennisapi-haystack 0.2.0 (released today): four new components — head-to-head, the 1968-2022 results archive (matches / player bios / careers), ranking tables, and in-play match statistics — plus new match filters (player/country/date-range/tour incl. juniors), graceful handling of tier walls, daily-quota 429s and ambiguous player names as readable Documents, and a logo. Authorship metadata now points at the livetennisapi org, and the branch is synced with main. PR body refreshed to match (the free tier is 100 requests/day).