Disclosure up front: I run the Live Tennis API, so this is vendor-authored — judge accordingly.
Proposal: live_scores/ — a concrete, real-API application of the polling/ patterns: a workflow that follows a live tennis match until it's final.
The polling/ family (frequent, infrequent, periodic_sequence) teaches the patterns against a mock test_service.py; this sample would show the same frequent-style shape against a real rate-limited API, where the retry policy and backoff have to handle actual 429s (free tier: 30 req/min, 100 req/day). The recently merged LiteLLM activity sample (#343) suggests externally contributed, real-service samples are in scope, which is why I'm asking here first.
Layout mirroring polling/frequent:
activities.py — httpx calls to /live and /fixtures, heartbeating activityworkflows.py — poll-until-final workflow, backoff tuned to the documented rate limitsrun_worker.py / run_frequent.py-style starterREADME.md — honest about cadence: the free tier suits developing/testing the sample, not fast continuous polling
I'd build it to repo conventions (uv, tests under tests/ if you want them) and will provide a free API key for whoever reviews so it runs without signup. If it's out of scope, no problem — happy to hear that too.
Disclosure up front: I run the Live Tennis API, so this is vendor-authored — judge accordingly.
Proposal:
live_scores/— a concrete, real-API application of thepolling/patterns: a workflow that follows a live tennis match until it's final.The
polling/family (frequent,infrequent,periodic_sequence) teaches the patterns against a mocktest_service.py; this sample would show the samefrequent-style shape against a real rate-limited API, where the retry policy and backoff have to handle actual 429s (free tier: 30 req/min, 100 req/day). The recently merged LiteLLM activity sample (#343) suggests externally contributed, real-service samples are in scope, which is why I'm asking here first.Layout mirroring
polling/frequent:activities.py— httpx calls to/liveand/fixtures, heartbeating activityworkflows.py— poll-until-final workflow, backoff tuned to the documented rate limitsrun_worker.py/run_frequent.py-style starterREADME.md— honest about cadence: the free tier suits developing/testing the sample, not fast continuous pollingI'd build it to repo conventions (uv, tests under
tests/if you want them) and will provide a free API key for whoever reviews so it runs without signup. If it's out of scope, no problem — happy to hear that too.