Build with Claude

You have access to the apinn API (real-time Pinnacle odds) via the "apinn" MCP tools
(or over HTTP: base https://api.apinn.io, header  X-API-Key: MY_KEY ).

GOAL — Build me a "DROPPING ODDS" monitor.
A dropping odd = an outcome whose decimal price has DROPPED (shortened)
significantly over time → a sign of sharp money / a steam move.

PARAMETERS (change as needed):
- sport       = 29         # 29=football, 33=tennis, 4=basketball
- market      = moneyline  # moneyline | spread | totals
- drop_pct    = 8          # minimum % drop to flag
- odds_min/max= 1.30 / 6.00    # ignore extremes
- refresh     = 60         # seconds between passes

METHOD:
1. Get live matches:
   GET /api/fixtures?sport_id={sport}&live=1
2. For each event, get the full odds history:
   GET /api/odds?event_id={id}&full_history=1&main_lines_only=1&market={market}
   (each row has a timestamp + odds1=home, odds0=draw, odds2=away ;
    todds1/0/2 = the same prices WITHOUT the margin — use them for a cleaner signal).
3. For each outcome, take the OPENING price (first snapshot) and the CURRENT price
   (last snapshot). Compute  drop% = (open − current) / open × 100.
4. Keep outcomes where  drop% ≥ drop_pct  AND  odds_min ≤ current ≤ odds_max.
5. Sort by drop% descending.
6. Print a table: match | market | outcome | open → current | drop% | minutes since open.
7. Re-run every {refresh}s ; only alert on NEW or increasing drops.

Every response returns quota headers (X-Quota-Remaining) — respect the limit (5,000 req/h).
Start now: list the current dropping odds.