Agentic search, powered by TypeSafe Jev

Agentic search API: more relevant results, fewer wasted tokens for your agent

Send one plain-language request to POST /ask. A decision model picks the engines and time window, scores every result, and drops off-topic and duplicate results before they reach your agent. Today that model is TypeSafe Jev.

Endpoint
POST https://api.search1api.com/ask
What this API helps you get

One natural-language request in, on-topic and deduplicated sources out, so your agent reads less and spends fewer tokens. A decision model, currently TypeSafe Jev, picks the engines and scores every result.

1
AI intent detection

Keyword query and time window from the request.

2
Engine routing

Up to 5 supported engines, searched in parallel.

3
AI reranking

Every result scored; off-topic results dropped.

Useful for

LLM agent tools / RAG retrieval / Community research

Your agent reads only the results that are on topic

A typical search tool returns each engine’s top results whether they fit or not, and your agent spends tokens reading all of them, often after trying several engines in turn. Ask makes those choices inside one call. A request such as "what are developers saying about Bun 1.3 this month" is typically routed to Hacker News, Reddit, and X plus general web engines, with a one-month window; "recent papers on speculative decoding" goes to arXiv. Every result is then scored against the request: results below 0.5 are dropped and duplicates across engines are merged, so the context you pass to your LLM is shorter and on topic.

AI Intent Detection

The decision model reads the request and picks the keyword query and time window.

Smart Engine Routing

The model scores supported engines, including Google, Reddit, Hacker News, GitHub, arXiv, X, and YouTube, and searches up to five in parallel.

AI Reranking

The model scores every result for relevance. Results below 0.5 are dropped, duplicates are merged, and each result keeps its score.

Flat 5 Credits, Model Included

A completed request costs 5 credits however many engines it searches. If no engine completes, the request is not charged.

What is a decision model, and why does agentic search need one?

A decision model does not generate text. It answers typed questions, such as yes or no, pick one of these, or how well does this fit, with calibrated probabilities. Searching well is a chain of exactly those decisions, so on every request Ask puts them to a decision model: which candidate keyword query best matches what the user means (and, for catalogues such as IMDb, the exact title), how well each supported engine fits the request, and whether the request implies a time window. Those answers drive intent detection and engine routing. After the search, the model is asked whether each returned result is about the subject; that probability is the relevance score used to rerank and filter results. Because the model returns decisions rather than prose, Ask never writes an answer of its own. Ask currently runs on Jev, TypeSafe AI’s System One model, called through TypeSafe’s API with the same model on Cloudflare Workers AI as a fallback, and we are gradually adding support for more decision models. Ask is a Search1API product, not an official TypeSafe product.

Agentic search pricing

Ask charges a flat 5 credits per completed request, whether it searches one engine or five, and the decision model calls are included. If some engines fail while others complete, the failures are listed in errors and the request is charged. If no engine completes, the API returns 502 and nothing is charged. New accounts start with 100 free credits, enough for 20 Ask requests.

Flat 5 credits per request, model calls included.

No charge when no engine completes (HTTP 502).

100 free credits on signup: 20 Ask requests, no credit card.

API key required; up to 30 requests per minute per account.

Implementation path

How an agentic search request runs

Send one plain-language request to POST /ask. A decision model picks the engines and time window, scores every result, and drops off-topic and duplicate results before they reach your agent. Today that model is TypeSafe Jev.

1

Intent detection: the decision model picks the keyword query, scores each engine for fit, and decides on a time window. Platform or time hints in the request, such as "on Reddit" or "this week", steer these choices.

2

Parallel search: up to five engines, from Google and DuckDuckGo to Reddit, GitHub, arXiv, and YouTube, are searched at once.

3

AI reranking: the model scores every result, results below 0.5 are dropped, duplicates are merged, and the list is sorted by relevance.

Best for

Agentic search API: a decision model (TypeSafe Jev today) picks the engines and scores every result, dropping off-topic and duplicate results so your agent reads less and spends fewer tokens

LLM agents on a token budget: one tool call returns reranked, citable sources instead of several pages of raw results.

RAG retrieval where choosing the right sources matters more than collecting the most results.

Research and monitoring across Reddit, Hacker News, X, GitHub, and arXiv, where the right sources change with every question.

FAQ

What is agentic search?

Agentic search hands the search decisions to a model instead of your code. You send a request in natural language; the model decides which keywords to use, which engines to search, and what time window applies, then judges which results are worth keeping. Ask makes those decisions in a single API call, one routing pass followed by reranking rather than a multi-step research loop, so latency and cost stay predictable.

How does Ask reduce token usage?

Three ways. Your agent makes one call instead of trying engines one by one; results scoring below 0.5 for relevance are dropped before the response is returned; and duplicates across engines are merged. Each result keeps its relevance score, so you can cut further before passing results to your model. Savings depend on the query, and a response holds at most 10 results and can hold fewer, or none.

Which decision model does Ask use?

TypeSafe’s Jev, called through TypeSafe’s API with the same model on Cloudflare Workers AI as a fallback. We are gradually adding support for more decision models.

How does Ask detect search intent?

Ask asks the decision model typed questions about the request: which keyword query fits best, how likely each engine is to help, and whether a time window is implied. Engines are chosen by those probabilities, up to five. The intent field in the response shows the keywords, engines, and window that were used.

How does Ask rerank results?

The decision model scores each result from 0 to 1 for whether it is about the subject of the request. Results below 0.5 are dropped, duplicates across engines are merged, and the rest are sorted by score. Each result keeps its relevance score so you can apply a stricter cut-off. The score is a model judgment, not a fact check.

When should I use Ask instead of Search?

Use Ask when you know what you want but not where to look. Use Search when you already know the engine and keywords and want that engine’s own ranking, filters, pagination, or Deep Search content.

How many credits does the Agentic Search API use?

A completed Ask request costs a flat 5 credits, however many engines it searches, with the decision model calls included. If no engine completes, the API returns 502 and the request is not charged.

Does Ask generate an answer?

No. Ask returns reranked results with titles, URLs, snippets, and relevance scores so your own LLM can read and cite them. It does not write a summary or an answer.

What data does Ask send to the decision model?

Your request and the titles and snippets of the returned results are sent to the Jev model for intent detection and scoring, through TypeSafe’s API or, as a fallback, Cloudflare Workers AI. The search itself runs through Search1API.

Can I use Ask from the SDKs or MCP?

Not yet. Call POST /ask over HTTP with an API key. The official SDKs, CLI, and MCP server do not include Ask, and it is not available through pay-per-request payments.