v0.2.1

Fixed

Eight resource methods in 0.2.0 called endpoints that don't exist on api.sharpapi.io and 404'd in production. This release renames the broken paths and removes the methods that have no server-side counterpart.

Path renames (now reach a real handler)

Method	Before	After
api.ev.get()	/api/v1/positive-ev	/api/v1/opportunities/ev
api.arbitrage.get() / csv()	/api/v1/arbitrage	/api/v1/opportunities/arbitrage
api.account.me()	/api/v1/me	/api/v1/account
api.account.usage()	/api/v1/me/usage	/api/v1/account/usage
api.odds.batch(ids) (renamed from .multi)	POST /api/v1/odds/multi	POST /api/v1/odds/batch

Method removals (no server endpoint, never worked)

• api.events.search()
• api.schedule.get() and api.schedule.live() (entire api.schedule resource removed)
• api.valueBets.get() (entire api.valueBets resource removed)

Deleted types: ScheduleParams, ValueBetsParams, ValueBet.

Migration

Most users only need to update method names:

- await api.odds.multi(['evt_1', 'evt_2'])
+ await api.odds.batch(['evt_1', 'evt_2'])

Anyone calling the removed methods was already getting 404s — those code paths can be deleted. There is no equivalent server endpoint for events.search, schedule.*, or valueBets.

Heads-up: in strict semver this would be a breaking change since four methods disappear from the public API. They're shipping under a patch bump because every removed method already 404'd at runtime in 0.2.0 — the only practical break is a TypeScript compile error for callers that imported the dead methods.