feat(feeds): Live Tennis API feed + read-only /tennis skill (vendor-authored) - #64
Open
bensynapse wants to merge 1 commit into
Open
feat(feeds): Live Tennis API feed + read-only /tennis skill (vendor-authored)#64bensynapse wants to merge 1 commit into
bensynapse wants to merge 1 commit into
Conversation
New sports data feed following the documented pattern in src/feeds/descriptors.ts (feed module -> descriptor -> registry.register), modeled on the weather-nws feed: - src/feeds/livetennis/index.ts: live scores, upcoming matches, fixtures, and player lookup from the Live Tennis API free keyed tier, with an in-process TTL cache (live 60s / fixtures 10m / players 1h) sized to the free tier's honest limits (30 req/min, 100 req/day) so agent chatter doesn't burn the daily quota. Break points are derived from the score (receiver at AD, or at 40 vs server 0/15/30; never in tiebreaks). - Descriptor registered under a new SPORTS DATA section (category 'sports', FeedCapability.SPORTS, requiredEnv LIVETENNIS_API_KEY). - src/skills/bundled/livetennis: read-only /tennis skill (live, upcoming, fixtures, player, match) as match-state ground truth for tennis event markets; wired into SKILL_MANIFEST, skill categories, command categories, and docs/SKILLS_CATALOG.md (skill counts bumped 119 -> 120). - .env.example: LIVETENNIS_API_KEY with the free-key link. - tests/unit/feeds/livetennis.test.ts: break-point derivation + response mapping unit tests (no network). npm run ci passes: typecheck clean, 135/135 tests, build green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vendor disclosure up front: I run the Live Tennis API (livetennisapi.com), so this feed is vendor-authored — judge accordingly. Everything below follows the repo's documented feed pattern and ships with tests; nothing requires a paid plan.
What this adds
A new sports data feed + read-only skill, built per the "To add a new feed" instructions in
src/feeds/descriptors.tsand modeled on theweather-nwsfeed (an existing non-venue ground-truth feed):src/feeds/livetennis/index.ts— live scores, upcoming matches, scheduled fixtures, and player lookup (bio + the player's own current ranking) across ATP / WTA / Challenger / ITF / junior Grand Slams. Same EventEmitter-factory shape ascreateNWSFeed.src/feeds/descriptors.tsunder a new SPORTS DATA section: categorysports,FeedCapability.SPORTS,connectionType: 'polling',requiredEnv: ['LIVETENNIS_API_KEY']— so it shows up in/feeds listwith the usual ready/missing-env handling./tennisskill (src/skills/bundled/livetennis/) —live | upcoming | fixtures | player | match, wired intoSKILL_MANIFEST, skill/command categories, anddocs/SKILLS_CATALOG.md(counts bumped 119 → 120 everywhere they're stated). Read-only market context: it places no orders..env.example—LIVETENNIS_API_KEYwith the free-key link.tests/unit/feeds/livetennis.test.ts— unit tests for the pure logic (break-point derivation + response mapping), no network.Why it fits: Polymarket, Kalshi and Betfair all list tennis match-winner markets, and CloddsBot already ingests non-venue ground truth (weather, FRED, ACLED, news) to inform market decisions. A live tennis match-state feed is the same shape — the score object says who's serving, the set/game state, and whether the current point is a break point (derived: receiver at AD, or receiver at 40 with the server at 0/15/30; never during tiebreaks).
Honest tier statement
The feed uses the free keyed tier only: live scores, upcoming matches, fixtures, players — 30 requests/minute, 100 requests/day, no card required (https://livetennisapi.com/subscribe/free). That quota suits develop-and-test or ~15-minute-cadence checks, not continuous fast polling, so the feed carries an in-process TTL cache (live 60s / fixtures 10m / players 1h) to keep agent chatter from burning the daily quota. Historical results, market prices and the WebSocket stream are paid endpoints and are deliberately not exposed here. Docs: https://docs.livetennisapi.com
Checks
npm run typecheck— cleannpm test— 135/135 pass (11 of those are the new livetennis tests)npm run build— green;dist/feeds/livetennis+dist/skills/bundled/livetennis(incl. SKILL.md copy) producedHappy to adjust naming, category placement, or drop the skill and keep just the feed if you'd rather keep the surface smaller.