canonical: https://jentic.com/apis/usa.gov/usagov-search-results-api

# USA.gov Search Results API

The USA.gov Search Results API (powered by Search.gov) provides programmatic access to search results from USA.gov and other federal government websites. It enables searching across federal web content with features like keyword highlighting, best bets, and spelling corrections. The API exposes 1 endpoints.

## For AI agents

Programmatically search web results. Covers 1 operations.

## Scope

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

## Capabilities

- Search web results
- Manage developer tools data programmatically
- Integrate USA.gov Search Results API into automated workflows
- Query and filter USA.gov Search Results API records by parameters
- Monitor USA.gov Search Results API operational status and events

## Use cases

### Developer Tools Operations

Use the USA.gov Search Results API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including search web results.

Example prompt: Call GET `/results/i14y` to search web results

### Data Retrieval and Monitoring

Query USA.gov Search Results 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 USA.gov Search Results API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call USA.gov Search Results 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/results/i14y` | Search web results |

## Key resources

- **search** — Search results operations

## Why Jentic

- **Setup:** Wiring the USA.gov Search Results API by hand means targeting its GSA search-gov host, shaping the i14y results query, and parsing the response yourself. Through Jentic you install once, import the USA.gov Search Results API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The USA.gov Search Results API exposes a single results endpoint whose search terms travel in the query rather than the URL path, so limit the agent to the operations it needs, such as fetching i14y results. You choose that operation set, so nothing beyond what you list runs.
- **Credential handling:** Your USA.gov credential 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 'search government web results', and Jentic returns the matching USA.gov Search Results API 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 USA.gov Search Results API use?

The USA.gov Search Results API uses no 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 search web results with the USA.gov Search Results API?

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

### What are the rate limits for the USA.gov Search Results 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 search web results through Jentic?

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

### How many endpoints does the USA.gov Search Results API have?

The USA.gov Search Results API exposes 1 endpoints covering search operations.

### Can I limit what my agent is allowed to do with the USA.gov Search Results API?

Yes. Jentic One runs self-hosted on your own infrastructure, and your own rules decide which operations and credentials the agent may use. The USA.gov Search Results API exposes a single results endpoint (GET `/results/i14y`) whose search terms travel in the query string rather than the URL path, so you can restrict the agent to just fetching i14y results and nothing else. Because you choose that operation set, no call beyond the ones you list runs.