@sorqen/resolver
v0.1.0
Published
Resolve supported Polymarket and Kalshi identifiers to canonical Sorqen sports IDs locally, offline and without venue credentials.
Maintainers
Readme
@sorqen/resolver
Resolve supported prediction-market identifiers into canonical Sorqen sports IDs locally.
No Sorqen API key, venue credential, account or network call is required for the resolver itself.
npm i @sorqen/resolverimport { kalshi } from '@sorqen/resolver';
const resolved = kalshi.resolveKalshi({
league: 'nfl',
eventTicker: 'KXNFLGAME-26SEP21NYGLAR',
knownAbbrevs: new Set(['NYG', 'LAR']),
marketType: 'moneyline',
selection: 'LAR'
});The result contains canonical Sorqen event/market/outcome identity when the ticker can be resolved unambiguously. Ambiguous or unparseable input returns no asserted match rather than guessing.
Where it fits
Sorqen's hosted API provides authenticated sportsbook-derived fair value. Prediction-market prices remain with the caller. The normal local workflow is:
- Fetch Sorqen fair value using a Free or paid Sorqen key.
- Fetch venue data using your own lawful venue access.
- Resolve the venue ticker locally with
@sorqen/resolver. - Compare locally with
@sorqen/client.
The resolver does not contain Sorqen fair-value data and cannot bypass Sorqen authentication or plan entitlements.
Why resolution is strict
Venue identifiers can encode compact team blocks, local dates, start times and doubleheader ordinals. Different sources also use different abbreviations for the same club. A wrong canonical match is more dangerous than an unmatched market, so the resolver refuses ambiguous inputs instead of choosing the most convenient-looking split.
Package boundary
@sorqen/resolver is MIT-licensed local code. It canonicalizes identifiers; it is not a Polymarket/Kalshi proxy and does not redistribute venue data.
Part of Sorqen.
