Knowledge Graph Search API

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

✓ Official Vendor SpecData EnrichmentCompany DataapiKey1 EndpointsREST

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.

Quickstart

Get started with Knowledge Graph Search API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search the google knowledge graph for an entity"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Knowledge Graph Search API 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

Limit results to a maximum number of entities per query

GET STARTED

Start building with Knowledge Graph Search API API

Explore with Jentic

View OpenAPI Document

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.

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

Use Cases

Patterns agents use Knowledge Graph Search API 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 though Jentic?

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

Credential isolation

The Google Cloud API key is stored encrypted in the Jentic vault and injected as the key query parameter at execution time. The agent never sees the raw key value.

Intent-based discovery

Agents search Jentic with phrases like 'search google knowledge graph' or 'look up entity by name' and Jentic returns the entities:search operation with documented query, types, and limit parameters.

Time to first call

Direct integration: 1-2 hours to enable the API, mint a key, and parse the JSON-LD response. Through Jentic: under 10 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Custom Search API

Custom Search returns web search results; Knowledge Graph Search returns canonical entity records

Use Custom Search when the agent needs links and snippets; use Knowledge Graph Search when it needs a structured entity record.

Complementary

Cloud Natural Language API

Natural Language extracts entities from text; Knowledge Graph Search resolves names to canonical IDs

Pair them: extract entities from a document with the Language API, then resolve each surface form to a Knowledge Graph entity.

Alternative

Clearbit API

Clearbit returns commercial firmographic data on companies and people; Knowledge Graph Search returns Google-curated public entity records

Choose Clearbit when the agent needs commercial sales-grade enrichment; choose Knowledge Graph Search for free, broad coverage of public entities.

FAQs

Specific to using Knowledge Graph Search API 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.