
For agent workflows, synchronous search is easier to reason about than a queue-plus-poll model.
Prismfy Team
April 17, 2026
For agent workflows, synchronous search is easier to reason about than a queue-plus-poll model.
You ask for evidence, wait for the response, and continue the loop. No extra job state. No second request. No stale intermediate status.
A synchronous API gives the agent a simpler control flow:
That is a cleaner developer experience than splitting the same action into job creation and result polling.
curl -X POST https://api.prismfy.io/v1/search \
-H "Authorization: Bearer ss_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "latest pricing changes for competitor",
"engines": ["brave", "bing"],
"timeRange": "week",
"language": "en"
}'
Synchronous search improves the workflow because:
That matters most when the search step is part of a short, interactive agent turn.
import requests
def search_now(query: str) -> list[dict]:
response = requests.post(
"https://api.prismfy.io/v1/search",
headers={"Authorization": "Bearer ss_live_YOUR_KEY"},
json={
"query": query,
"engines": ["brave", "bing"],
"timeRange": "week",
"language": "en",
},
timeout=30,
)
response.raise_for_status()
return response.json().get("results", [])[:3]
results = search_now("latest pricing changes for competitor")
print(results)
If you want a simpler agent search flow, start with Prismfy docs and use synchronous POST /v1/search calls inside your loop.
Try it free
Free tier includes 3,000 requests per 30 days. No credit card required.