Skip to main content
vertical is part of every routing intent. It tells Speko which benchmark slice to score against.
VerticalUse for
generalConversational AI, default catch-all.
healthcareClinical dictation, patient intake, telehealth. Boosts providers with strong medical terminology accuracy.
financeBanking, insurance, fintech support. Boosts providers with numeric and entity recall.
legalDepositions, contract review, legal intake. Boosts providers tuned for formal English and proper-noun density.
Vertical does not change the request shape — it changes which providers/models score highest. A healthcare STT call may route to a model with medical-corpus fine-tuning even when a generalist model is cheaper.

​
Picking a vertical

Use the most specific applicable vertical. A general intent will route to a generalist model even when a domain-tuned one would be better for your traffic. If your traffic is mixed, segment at request time — set vertical per call based on the user, route, or session metadata. Speko pays no penalty for varying vertical across calls; each call routes on its own.

​
Compliance vs vertical

Vertical biases provider scores. It does not restrict providers to BAA-covered ones, EU-resident ones, etc. Use constraints for compliance-driven allow-lists.