canonical: https://jentic.com/apis/serpstack.com/serpstack

# serpstack API

Real-Time & Accurate Google Search Results API with JSON REST responses for SERP data. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically execute google search. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Execute Google search
- Manage developer tools data programmatically
- Integrate serpstack API into automated workflows
- Query and filter serpstack API records by parameters
- Monitor serpstack API operational status and events

## Use cases

### Developer Tools Operations

Use the serpstack API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including execute google search.

Example prompt: Call GET /search to execute google search

### Data Retrieval and Monitoring

Query serpstack API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary serpstack API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call serpstack API 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 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/search` | Execute Google search |

## Key resources

- **search** — Operations related to search

## 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:** 46 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/serpstack.com/serpstack/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 serpstack by hand means appending your access_key query parameter to every search request and choosing between the HTTP free-tier and HTTPS hosts yourself. Through Jentic you install once, import serpstack from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** serpstack passes the access_key as a query parameter and exposes a single search endpoint, so limit the agent to the operation it needs, which is running a search. You choose the operations it may call, so it holds only that capability.
- **Credential handling:** Your serpstack access 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 'execute a Google search', and Jentic returns the matching serpstack operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the serpstack API use?

The serpstack API uses an API key passed in the `access_key` query. 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 execute google search with the serpstack API?

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 serpstack API?

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 execute google search through Jentic?

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

### How many endpoints does the serpstack API have?

The serpstack API exposes 1 endpoints covering search operations.

### Can I limit what my agent is allowed to do with the serpstack API?

Yes. The serpstack API exposes a single endpoint, GET /search for running a Google search, and because Jentic One is self-hosted your own rules decide which operations and credentials the agent may use. You can restrict the agent to just that search operation, so it holds only the capability to run searches and nothing more. The access_key is stored encrypted by your own instance and injected at execution time, so the agent calls the endpoint without ever seeing the raw key.