ceven

Search api

Feeds live search engine results and structured web data into your workflows to automate market research, competitor tracking, and lead discovery.

Try Search api in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Search api integration

    • Describe the outcome and Ceven picks the right Search api calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Search api data, across all 5 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Search api access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Search api, when, and on whose behalf.
    • The agent pauses and asks when Search api is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Search api.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Search api action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Search api, and when to use it.

Search
Use this to perform a unified search across Google, Bing, Yahoo, and others. Pull structured data for keywords or specific sites.
Get Account Info
Pull current account usage, remaining credits, and subscription period to monitor API spend.
Get Cached Search by ID
Retrieve a previous search result by its ID in JSON format to avoid using extra credits for the same query.
Get Cached Search HTML by ID
Pull the raw HTML snapshot of a previous search execution for deep auditing or legal evidence.
Get Locations
Pull the list of available location identifiers to target search queries to specific geographic areas.
Google Search
Run a targeted query specifically on Google to pull organic results, news, and knowledge graph data.
Bing Search
Execute a search on Bing to compare SERP rankings against Google results.
YouTube Search
Pull video results, channel data, and view counts for specific keywords.
Amazon Search
Retrieve product listings, prices, and ratings for market research.
DuckDuckGo Search
Perform a privacy focused search to gather alternative web data.
Yahoo Search
Pull search results from Yahoo to broaden the data set for SEO analysis.
Search News
Filter results specifically for recent news articles across multiple engines.

12 actions · scroll to see them all

Frequently asked questions

Search API manages the entire infrastructure required to bypass bot detection. When Ceven triggers a request, the platform routes the query through a massive network of residential and data center proxies. They handle the solving of CAPTCHAs and the rotation of user agents in the background. This means your workflows never fail due to an IP ban or a challenge screen. You receive a clean JSON response containing only the data you requested, while the complexity of maintaining a stealthy scraping footprint is handled entirely by the vendor. This allows you to scale your search volume without needing to build your own proxy management system.
Yes. You can use the Get Locations tool to find the exact location identifier for a specific city or region. Once you have that ID, you pass it into the search request. This forces the search engine to return results as if the query were coming from a user in that exact location. This is critical for local SEO tracking or analyzing how local businesses appear in different markets. Ceven can automate this by looping through a list of city IDs and pulling the top results for each, creating a comprehensive map of your local search visibility across different geographic zones.
JSON results are structured data. They provide clear fields for titles, snippets, and links, which makes them ideal for feeding into an AI model or a database. HTML results are raw snapshots of the page. These are useful when you need to verify exactly how a page looked at a specific moment or when you need to extract data from a part of the page that the JSON parser missed. In Ceven, use JSON for automation and HTML for auditing. Since both are cached, you can retrieve them using the search ID without spending additional credits for a new live search.
Yes. Search API enforces rate limits based on your specific subscription tier. Some tiers have hourly limits on the number of requests you can send, while others are gated by a monthly credit quota. If you exceed these limits, the API will return an error code indicating that you have been rate limited. Ceven can help manage this by using the Get Account Info tool to check your remaining credits before starting a large batch job. If you are on a lower tier, we recommend scheduling your workflows to spread requests across several hours to avoid hitting the hourly cap.
The unified search tool provides access to over 40 different engines. This includes the major players like Google, Bing, and Yahoo, as well as specialized platforms like YouTube for video data and Amazon for product data. It also covers alternative engines like DuckDuckGo. This breadth allows you to build a single workflow in Ceven that gathers a holistic view of the web. Instead of managing 40 different API keys and data formats, you use one interface and receive consistent JSON output regardless of which search engine provided the original result.
Cached results are stored for a limited window after the initial search is performed. This allows you to retrieve the same data multiple times without incurring new costs. However, these caches are not permanent archives. If you need to keep a record of search results for long term analysis or legal compliance, you should use a Ceven workflow to save the JSON or HTML output into your own database or cloud storage like S3 or Google Drive. Relying on the Search API cache for permanent storage is not recommended as the data will eventually expire.
Search API is primarily a SERP tool, meaning it is designed to scrape search engine result pages, not every individual page on the internet. It provides the links and snippets found in search results. To get the full content of a specific page, you would typically use the link provided in the Search API response and then pass it to a dedicated web scraping tool. While the HTML cache gives you the snapshot of the search page, it does not give you the full content of the destination websites. You can chain Search API with other scraping tools in Ceven to achieve a full end to end extraction.
Yes. Unless you are specifically requesting a cached result by ID, every search request triggers a live query to the search engine. This ensures that the data you receive reflects the current state of the web, including the latest news and ranking changes. Because the platform handles proxy rotation and CAPTCHAs in real time, there is very little latency between your request and the delivery of the results. This makes it suitable for high urgency tasks like monitoring breaking news or tracking flash sales across different e commerce platforms.

Alternatives to Search api

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

SerpApi logoSerpApiBright Data logoBright DataOxylabs logoOxylabsValueSerp logoValueSerp

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Search api and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free