canonical: https://jentic.com/apis/searchapi.io/searchapi

# SearchAPI Google Search

SearchAPI provides a real-time Google Search scraping API. Retrieve organic results, knowledge graphs, ads, and more from Google search results programmatically. The API exposes 3 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically perform a google search, list available locations. Covers 3 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Perform a Google search
- List available locations
- Get account information
- Query and filter SearchAPI Google Search records by parameters
- Monitor SearchAPI Google Search operational status and events

## Use cases

### Communications Operations

Use the SearchAPI Google Search to perform communications operations programmatically. The API provides 3 endpoints covering core functionality including perform a google search, list available locations, get account information.

Example prompt: Call GET /search to perform a google search

### Automated Google Search Management

Automate google search operations by combining multiple SearchAPI Google Search endpoints. Agents can list available locations and then get account information in a single workflow.

Example prompt: Call GET /locations to list available locations, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SearchAPI Google Search endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'perform a google search', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/search` | Perform a Google search |
| GET | `/locations` | List available locations |
| GET | `/account` | Get account information |

## Key resources

- **Google Search** — Google search scraping endpoints
- **Utilities** — Utility and account endpoints

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 38 / 100
  - AI Discoverability: 83 / 100
- **View full report:** https://jentic.com/apis/searchapi.io/searchapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SearchAPI Google Search by hand means picking between its query api_key and bearer token, threading the key onto every /search call, and handling result pagination and rate limits yourself. Through Jentic you install once, import SearchAPI Google Search from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SearchAPI Google Search exposes read-only lookups (/search, /locations, /account) that take their query in the request parameters rather than a resource in the URL path, so scope by operation: limit the agent to the operations it needs, such as running a search or listing supported locations, and leave the rest out.
- **Credential handling:** Your SearchAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'run a google search' or 'list supported search locations', and Jentic returns the matching SearchAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the SearchAPI Google Search use?

The SearchAPI Google Search uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I perform a google search with the SearchAPI Google Search?

Yes. Use the GET /search endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SearchAPI Google Search?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I perform a google search through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'perform a google search'. Jentic returns the matching SearchAPI Google Search operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SearchAPI Google Search have?

The SearchAPI Google Search exposes 3 endpoints covering google search, utilities operations.

### Can I limit what my agent is allowed to do with the SearchAPI Google Search?

Yes. Because you run Jentic One yourself, your own rules decide which SearchAPI Google Search operations and credentials the agent can use. Since every endpoint here is a read-only lookup, you scope by operation: allow only the calls the agent needs, such as GET /search to run a query or GET /locations to list supported locations, and leave the rest, like GET /account, out. Your SearchAPI key stays encrypted in your instance and is injected only for the operations you permit.