Skip to main content
Use a routed Recipe when your application needs results across providers through one request. Locus selects eligible providers, merges their results, and returns sources and a billing receipt. For the full set of outcomes and use cases, start with Recipes. This page covers server-side search and flight routing.

Choose an endpoint

Costs vary with the providers used. These routes charge for successful underlying calls; preview requests are free.

Configure the eligible pool

Open Agent tools → Multi-Provider Web Search to set the provider allowlist, search breadth, and result limit. Providers must also have an enabled catalog access path. Your allowlist is a hard boundary. A request can narrow it further but cannot add providers outside it.

Preview without calling providers

Append /preview to the execution route to see the planned providers and estimated charge:
A preview spends no credits. Availability and prices can change before execution, so pass maxCredits to set an execution-time ceiling.
The main controls are search mode, result count, recency, country, domains, and the credit ceiling. If the estimated charge exceeds maxCredits, Locus rejects the plan before dispatch without charging. Reuse the idempotency key when retrying the same logical request. Use a new key for a new request.

Read the result and receipt

The response includes results, provider outcomes, and billing.chargedCredits. A partial: true response means some providers failed while others produced results. Review those results before requesting more work; successful calls can still be charged. Agents discover these routes through their normal tool search. Connection allowlists and spending limits continue to apply.

Compare flights with Locus Travel

Call locus-travel/flight-search/preview with airports, dates, and preferences. Execute the same body at locus-travel/flight-search with an idempotency key.
Results include itineraries, provider sources, warnings, booking availability, and the exact charge. If the route returns 202, retry the same request with the same idempotency key to collect the result. See the API reference for all filters, response fields, and workspace routing settings.