Google Custom Search API (Programmable Search Engine) returns Google web search results scoped to one or more sites or to the wider web. It exposes a single endpoint that accepts a query, a custom search engine ID, and optional filters such as result language, safe-search level, country restriction, and start offset for pagination. A site-restricted variant returns only results from the configured engine's domains. Output includes title, snippet, link, and rich result metadata that match what end users would see on google.com.
2 endpointsThe Fact Check Tools API exposes Google's index of ClaimReview-marked-up fact checks published across the open web. Developers can search published fact checks by claim text, by image, or by topic, and publishers can manage their own ClaimReview pages programmatically — creating, listing, updating, and deleting page entries that Google ingests into the index. The API is the canonical interface for both consuming third-party fact-check signals and contributing publisher claim reviews.
7 endpointsThe Google Civic Information API provides US-focused civic data — elected officials, polling locations, election information, and political divisions — keyed by postal address or OCD division identifier. It is widely used by civic-tech apps, voter-engagement tools, and journalism projects to surface representatives and ballot information for a given address. The API is small (six endpoints) but covers the main lookups needed for representative info and election day support.
6 endpointsThe Knowledge Graph Search API exposes a single endpoint that searches Google's Knowledge Graph for entities — people, places, organizations, films, and other notable things — and returns Schema.org-formatted results with names, descriptions, types, image URLs, and detailed descriptions. It is intended for autocomplete experiences, entity disambiguation, and enrichment of internal records with canonical Google identifiers. The API is read-only and works with a simple API key.
1 endpointsThe Travel Impact Model API returns carbon dioxide equivalent (CO2e) emission estimates for individual flight legs based on Google's Travel Impact Model. Given an origin airport, destination airport, operating carrier, flight number, and departure date, the API returns per-passenger emissions broken out by cabin class along with the model version used. It is designed for travel platforms, sustainability dashboards, and reporting systems that need consistent, comparable flight emissions data.
1 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.