USA.gov Search Results API

Name: USA.gov Search Results API
Brand: USA.gov Search Results API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlnone1 EndpointsREST

Install Jentic One Beta

Connect the USA.gov Search Results API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the USA.gov Search Results API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fusa.gov%2Fusagov-search-results-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fusa.gov%2Fusagov-search-results-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with USA.gov Search Results API.

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

GET STARTED

Start building with USA.gov Search Results API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use USA.gov Search Results API for, with concrete tasks.

★ 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.

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.

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.

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using USA.gov Search Results API through Jentic.

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.