https://vaaya.ai/api/run/linkup/deep-searchPOST /api/run/linkup/deep-search · x402 API by vaaya
Linkup — DEEP agentic search: iterative multi-query retrieval for hard or multi-hop questions where one-pass search misses. Same params as linkup/search (`q` + outputType/dates/domain filters). Slower (tens of seconds) and 5× the price — escalate here only after linkup/search or exa/search come back thin. For full multi-step research reports, parallel/task (10-30¢) is the bigger rung.
What does this x402 API do?
https://vaaya.ai/api/run/linkup/deep-search. This is an x402-gated POST API resource from vaaya. TOLL·402 did not invoke this route automatically because doing so was not considered safe. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- TOLL·402 did not invoke this route automatically because doing so was not considered safe
- Resource ID
- 1c38a68b420ff3b8c46cd62a
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://vaaya.ai/api/run/linkup/deep-search", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"q"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Registry record checked
Registry health: healthy.
- Origin reachable
HEAD https://vaaya.ai/ returned 200.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.