The Tevos Score, over the wire.
One endpoint. Signed requests. Rate-limited per partner. First integrations ship in 2026 — access is private until the contract surface stabilises. Email us with your use case and we'll loop you in early.
Three things you can wire up
Match scoring
Score a candidate against your roles in real time. Return a ranked list with confidence and reasoning.
Voice-AI screening
Structured candidate-recorded screens with auto-graded transcripts (LLM-driven outbound calls on the roadmap).
Benchmark intelligence
Pull live, anonymised compensation bands by role family, level, and city tier.
How you get a key
Tell us your use case
Email hello@gettevos.com with the integration target (your ATS / your platform / internal HRIS). Include expected volume.
Sign a partner agreement
Covers our SLA, your re-id and retention obligations, and our acceptable-use policy.
We pair you with an engineer
Until self-serve keys ship, integrations are stood up case-by-case with rate-limited shared credentials and a partner-specific contract.
What we'll commit to, and what we won't yet
- We're not running a public SLA yet — partner SLAs are negotiated per-contract.
- Latency budgets are tracked internally; no public p99 commitment until the partner cohort stabilises.
- Webhook delivery (signed, retried) is on the roadmap — until then, polling is the only supported integration mode.
- Region pinning is on the roadmap. Today everything runs out of a single primary region.
Why the surface is small — on purpose
The wire shape, scopes, signature scheme, rate limits, and SDK surface live in the partner portal. This is intentional — we keep the surface narrow so we can move it without breaking partners, and so the matching graph stays defensible.
Send us a use case →
Tell us where the Tevos Score should land. We'll write back.
hello@gettevos.com →