Google Knowledge Graph Search API

Name: Knowledge Graph Search API
Brand: Knowledge Graph Search API
Availability: InStock

✓ Official Vendor SpecData EnrichmentCompany DataapiKey1 Endpoints

Install Jentic One Beta

Connect the Knowledge Graph Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Knowledge Graph Search 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 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 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 Knowledge Graph Search API.

Search the Knowledge Graph by free text query and return ranked entity matches

Filter entity results by Schema.org type such as Person, Organization, or Movie

Restrict results to a specific language for localized names and descriptions

GET STARTED

Start building with Knowledge Graph Search API

Explore with Jentic

View OpenAPI Document

For Agents

Search the Google Knowledge Graph for entities and return Schema.org JSON-LD results with names, types, descriptions, and images. Useful for entity enrichment and autocomplete.

Use for: Search the Google Knowledge Graph for 'Marie Curie', Find all Knowledge Graph entities matching 'Apple' filtered to Organization, Look up an entity by its kg machine id, I want to enrich a contact record with a Knowledge Graph identifier

Not supported: Does not write to the Knowledge Graph, return web search results, or expose entity relationships beyond the @type field - use only for read-only entity lookup.

Use Cases

Patterns agents use Knowledge Graph Search API for, with concrete tasks.

★ Entity enrichment for CRM records

Marketing and sales operations teams enrich company and contact records with stable Knowledge Graph IDs so multiple internal systems can refer to the same canonical entity. A single GET /v1/entities:search call with a company name and types=Organization returns ranked candidates with descriptions and image URLs the agent can use to confirm a match.

Search the Knowledge Graph for query 'Stripe' with types=Organization and limit=3, then return the top result's @id, name, and description.

Autocomplete for entity pickers

Apps that let users tag content with people, films, or places call entities:search as the user types. Each request returns ranked entity matches with image URLs and short descriptions, which is enough to render a rich dropdown without maintaining an internal entity database.

On each keystroke, call entities:search with the partial query and limit=5, then render the resulting names and image URLs in the dropdown.

Disambiguating ambiguous names

When a user types a query like 'Mercury' the same string can refer to a planet, a chemical element, a band, or a brand. The Knowledge Graph Search API returns ranked candidates with type and description so an agent can surface a disambiguation list rather than guessing which Mercury the user meant.

Call entities:search?query=Mercury&limit=5 and present each result's @type and description so the user can pick.

Agent-driven knowledge enrichment via Jentic

An agent answering questions about real-world entities can call the Knowledge Graph Search API through Jentic without managing API keys. Jentic surfaces the single search operation in natural language and returns the schema, so the agent can cite Google's canonical entity description when grounding its answer.

When asked 'who is Hedy Lamarr', call google_kgsearch_query with query='Hedy Lamarr' and return the top result's detailedDescription.articleBody.

Key Endpoints

1 endpoints — the 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.

METHOD

PATH

DESCRIPTION

GET

/v1/entities:search

Search the Knowledge Graph for entities by query, types, language, and limit

GET

/v1/entities:search

Search the Knowledge Graph for entities by query, types, language, and limit

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google Cloud API key is stored once, encrypted, by your own Jentic One instance and injected at execution time as the key query parameter. The raw key value never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search the google knowledge graph' or 'look up an entity by name', and Jentic returns the entities:search operation with its query, types, and limit parameters so the agent calls it correctly without browsing the reference docs.

Time to first call

FAQs

Specific to using Knowledge Graph Search API through Jentic.

What authentication does the Knowledge Graph Search API use?

A simple API key passed as the key query parameter. The spec lists no OAuth scheme, so the only credential is a Google Cloud API key with the Knowledge Graph Search API enabled. Through Jentic the API key sits in the encrypted vault and is injected at execution time.

What types can I filter Knowledge Graph results by?

The types parameter accepts any Schema.org type, with Person, Organization, Place, Movie, Book, and Event being the most common. Pass multiple types to broaden the search, e.g. types=Person&types=Organization.

What are the rate limits for the Knowledge Graph Search API?

Google's default quota is 100,000 queries per day per project with a per-second burst limit set per API key. Quotas can be raised in the Cloud console for high-volume autocomplete use cases.

How do I look up an entity through Jentic?

Run jentic search 'search the google knowledge graph' to find GET /v1/entities:search, jentic load to fetch its parameters, then jentic execute with query, types, languages, and limit. Jentic handles the API key transparently.

Can I retrieve an entity by its Knowledge Graph ID?

Yes. Pass the machine id as the ids query parameter on /v1/entities:search to fetch a specific entity directly without a free-text query.

Is the Knowledge Graph Search API free?

There is no per-call charge - usage is bounded only by the daily quota of 100,000 queries per project. Higher tiers require a quota increase request through Google Cloud.

Can I limit what my agent is allowed to do with the Knowledge Graph Search API?

Yes. This API exposes a single read-only operation, the GET /v1/entities:search entity lookup, and because you run Jentic One yourself your own rules decide which operations and credentials your agent may use. You can scope the agent to just that search operation, so it can look up entities by query, types, language, or machine id but can never write to the Knowledge Graph. Your Google Cloud API key is stored once by your own instance and injected at execution time, so the agent calls the endpoint without ever seeing the raw key.