HyperSpectral · SpecAI
Sign in to run spectral matching and manage API keys.
or sign in with a password
Run one spectrum against a catalogue and see how the model ranks it. For the request and response shapes, see the Docs tab.
Raw and unnormalized. The service applies the sqrt and max-normalization the model was trained with.
Enter a spectrum, then run a match.
A catalogue is the set of candidate structures a spectrum is ranked against. It is loaded once from a file and is then final. Only exact mass is searched; the model does the rest. Every entry needs a structure, so a list of names and masses alone cannot be used.
Loading…
Choose a catalogue on the left.
Keys authenticate scripts and integrations. The portal itself uses your session, so you only need a key for programmatic access. A key carries the full integration surface for this account: models, catalogues, and matching. The secret is shown once and is not recoverable.
A key acts with owner-level access to this account and reaches no other account. It cannot grant platform admin. Treat it as you would the account password: it can mint further keys for this account, so revoke rather than reissue if one is exposed. A narrower key can be requested through the API by naming scopes explicitly.
Loading…
The reference below is rendered from this deployment's OpenAPI document, so it always describes the running build. It covers the integration surface authenticated with an API key; portal sign-in and account administration are operator functions and are excluded.
Constraints that affect correctness (the adduct is never inferred, isomers share an exact mass, a truncated candidate set is not a ranked shortlist, scores are not probabilities) are documented in the specification itself and appear in the description below.