Model Selection

Choose Parasail models by capability, product, latency, cost, and validation workflow instead of relying on stale static rankings.

Model availability and capabilities change frequently. Instead of relying on a static recommendation table, use this guide to choose a short list of candidates, check availability with the live models endpoint, and evaluate the models against your own prompts before committing to production.

To list currently available serverless models, use the /v1/models endpoint.

Start with the workload

Workload	What to optimize for	Start here
Chat and text generation	Instruction following, latency, context length, and cost	Chat and text generation
RAG and embeddings	Embedding quality, retrieval latency, output size, and throughput	RAG and embeddings
Agents and tool calling	Tool-call reliability, structured outputs, multi-turn behavior, and latency	Agents and tool calling
Vision and multimodal understanding	Image input quality, input size, and task success	Multi-Modal

Choose the right product

Product	Best fit	Notes
Serverless	Fast experiments and production traffic on models already hosted by Parasail	Use the models endpoint to check availability before wiring a model into an application.
Elastic Endpoints	Dedicated GPU performance with per-token billing and no idle-GPU bill for eligible models	Contact sales to confirm model eligibility and set up your endpoint. Availability is limited to selected models and expands model by model.
Dedicated Instances	Private models, custom Hugging Face models, predictable capacity, or model settings that need full endpoint control	Start in the UI when possible so the compatibility checker can validate model and hardware choices.

Check live availability

Use the models endpoint before committing to a model name:

curl https://api.parasail.io/v1/models \
  -H "Authorization: Bearer $PARASAIL_API_KEY"

The response lists the serverless models available to your account. For Dedicated Instances, use the deployment flow or the Dedicated compatibility checks to validate public or private Hugging Face model IDs.

The serverless models response doesn't establish Elastic Endpoints eligibility. Contact sales to confirm eligibility and set up your endpoint, and see Elastic Endpoints for pricing and capacity.

Evaluate candidates

Use the same representative prompts, documents, tool schemas, or images for every candidate. Track these dimensions:

• Quality: task success rate, factuality, formatting reliability, and human review scores.

• Latency: time to first token for streaming and total response time for non-streaming calls.

• Cost: token usage, output length, and deployment size.

• Context fit: maximum input size, retrieval chunk size, and expected output length.

• Feature support: structured output, tool calling, multimodal input, streaming, and Responses API support where required.

• Operational fit: rate limits, quota requirements, retry behavior, and monitoring needs.

Run a repeatable evaluation

Use one evaluation set for every candidate model.

1. Collect representative prompts, documents, images, tool schemas, or expected JSON schemas from your product.

2. Run the same inputs through each candidate model.

3. Save the raw request, raw response, latency, token usage, and pass/fail result for each input.

4. Review failures by category: wrong answer, bad format, missing tool call, hallucination, timeout, or cost outlier.

5. Promote only models that meet your quality, latency, cost, and feature-support thresholds.

Run evaluations through Serverless or Dedicated endpoints and record each result with a stable input identifier.

For private or fine-tuned models, start with Dedicated Instances and validate the model ID in the deployment flow before running a full evaluation.

Validate feature-specific requirements

Some workloads need more than general text quality:

• For JSON or schema-constrained output, test the model with Structured Output.

• For function calling and agent loops, test the model with Tool/Function Calling and the Responses API.

• For multimodal prompts, test with the exact image or document types described in Multi-Modal.

• For embeddings, measure retrieval quality on your own corpus.

Next steps

• Models endpoint—list available serverless models

• Serverless overview—make interactive OpenAI-compatible calls

• Elastic Endpoints—use private capacity with per-token billing for eligible models

• Dedicated Instances overview—deploy public or private models