NewJoin us for our inaugural conference, Forge 2026

Semantic search as fast as people type

Fireworks is the open-model platform for search. Run open embedding and reranking models on one API, beside the model that writes the answer. Notion’s Head of AI Engineering: “Latency is perceived as search quality.”

Search

What is search?

Search is retrieval that matches a query’s intent with embeddings, often fused with keyword (BM25) results, then reranks the candidates by relevance.

You can build semantic product search, in-app search, knowledge retrieval for agents, deep-research search agents and recommendation engines. On Fireworks, the engineers adding semantic search to a product own the stack.

Query understanding

Llama 3.1 8B Instruct classifies the query’s intent before you embed and retrieve.

Embed and retrieve

Qwen3 Embedding 8B turns documents and queries into vectors you store in your own vector database.

Rerank

Qwen3 Reranker 8B reorders your top candidates through the /rerank endpoint and returns a relevance score for each.

How search runs on Fireworks

Run every model hop on Fireworks and keep vectors in the store you already use.

Inference

Start on serverless Qwen3 Embedding 8B and Qwen3 Reranker 8B, then move to a dedicated deployment when you need the Voyage family.

Training

When a generic model misses your latency budget, fine-tune a smaller open one, the way Notion cut latency from about 2 seconds to 350 ms.

Orchestration

Orchestration barely applies to search because each hop calls a fixed model; use Nexus if you orchestrate answer generation across models and hold a budget.

Why use Fireworks for search?

What you get when one platform serves every model hop

One client

Point your OpenAI client at Fireworks by changing the base URL and model name.

Pay per token

Embed at $0.10 and rerank at $0.20 per 1M tokens on serverless.

Tune to domain

With RFT, Genspark beat a closed model by 12% on quality at half the cost.

Spiky traffic

Sentient got 25–50% more throughput per GPU for search under spiky load.

Buyer's checklist

What to look for in a search platform

Whole-pipeline latency

Ask for latency on a full query, from query understanding to the generated answer.

Latency under concurrency

Load-test at 20–50 parallel requests and track p95 and TTFT.

Quality on your domain

Generic embedders miss your vocabulary. Check that you can fine-tune the models in your path.

Vector database fit

Vectors should load into your store. A Fireworks cookbook uses MongoDB $vectorSearch.

Cost per query

Add up tokens across every hop of a query. Per-token pricing lets you do that math before launch.

Cold-start behavior

Ask what the first request after an idle period returns, and plan your retries around it.

How it works

How to set up search on Fireworks

Step 1: Point your OpenAI client

Create a Fireworks API key and set base_url to https://api.fireworks.ai/inference/v1.

Step 2: Embed your corpus

Call fireworks/qwen3-embedding-8b on your documents. Set dimensions to fit your index and L2-normalize vectors for cosine.

Step 3: Store vectors in your database

Write vectors to the store you already run, then recall your top candidates with vector search.

Step 4: Rerank the candidates

Send the query and your top candidates to /rerank with fireworks/qwen3-reranker-8b. Results come back ordered by relevance.

Step 5: Generate or fine-tune

Pass reranked results to a generator. Fine-tune it with LoRA when off-the-shelf answers miss your domain.

Models

Which models can I use for search?

Start with serverless Qwen3 Embedding 8B and Qwen3 Reranker 8B, then add a generator. The Voyage family, including Voyage Multimodal 3.5, runs on dedicated deployments.

Guide

How to tune latency for search

Measure the whole pipeline

Time one query end to end: query understanding, embedding, vector recall, rerank and generation. Then repeat it at 20–50 parallel requests and read p95 and TTFT, since single-hop benchmarks hide the rest of the chain. Your user waits on the slowest hop.

Pick serverless or dedicated

On serverless, you pay per token for Qwen3 Embedding 8B and Qwen3 Reranker 8B. A dedicated deployment runs the Voyage family and scales to zero when idle, so the first request after idle can return a 503 during cold start. Build the retry in.

Choose multi-LoRA or live merge

Live merge matches base-model latency, so pick it when one adapter carries your search traffic. Multi-LoRA loads many adapters onto one dedicated base deployment, which is how Cresta cut cost up to 100x vs. GPT-4. You pay with TTFT often 10–30% higher and lower throughput under load.

FAQ

Frequently asked questions about search

Can I generate text embeddings on Fireworks?

Yes. Qwen3 Embedding 8B runs serverless on the /embeddings endpoint. Qwen3 Embedding 4B and 0.6B and the Voyage family run on dedicated deployments.

What do embedding and reranking cost?

On serverless, Qwen3 Embedding 8B is $0.10 per 1M tokens and Qwen3 Reranker 8B is $0.20 per 1M tokens.

Is the embeddings API OpenAI-compatible?

Yes. Point the OpenAI client at https://api.fireworks.ai/inference/v1 and pass a Fireworks model name. Reranking uses a separate /rerank endpoint.

Should I use serverless or dedicated?

Start on serverless with Qwen3 Embedding 8B and Qwen3 Reranker 8B. Move to a dedicated deployment for the Voyage family, and retry the first request after idle, which can return a 503.

Where does my search data go?

Fireworks doesn’t log or store prompt or generation data for open models unless you opt in. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256).

How is search different from Enterprise RAG?

Use search for retrieval quality and speed: embedding and reranking. Use Enterprise RAG for grounded generation over your internal documents.

Search as fast as people type

Run open embedding and reranking models on one API, beside the model that writes the answer.