Google Discovery Engine API

Name: Discovery Engine API
Brand: Discovery Engine API
Availability: InStock

✓ Official Vendor SpecAI/MLEmbeddings Searchoauth275 EndpointsREST

Install Jentic One Beta

Connect the Discovery Engine API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Discovery Engine 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 Discovery Engine API.

Run semantic search and autocomplete over a custom data store of documents

Train and serve custom search ranking models on a data store

Ground LLM responses against indexed content via the groundingConfig:check endpoint

GET STARTED

Start building with Discovery Engine API

Explore with Jentic

View OpenAPI Document

For Agents

Run semantic search, recommendations, and RAG-grounded conversations over your own data via Vertex AI Search.

Use for: Search a Vertex AI Search data store for documents matching a query, Check whether an LLM answer is grounded against indexed content, Train a custom search ranking model on a data store, Get autocomplete suggestions for a partial query

Not supported: Does not host raw LLMs, train embedding models, or manage GPUs - use for managed retrieval, ranking, and grounding via Vertex AI Search only.

Use Cases

Patterns agents use Discovery Engine API for, with concrete tasks.

★ Enterprise Semantic Search

Build a private semantic search experience over indexed enterprise documents. The completionConfig:completeQuery endpoint provides autocomplete; the search endpoints (under data stores) return ranked results with snippets. Teams swap out keyword search for semantic ranking without managing embeddings or vector indexes themselves.

Call completeQuery on completionConfig 'projects/p/locations/global/dataStores/ds/completionConfig' with input 'reset pass' and return the top 5 suggestions.

RAG Grounding Verification

When a downstream LLM produces an answer, call groundingConfig:check to verify the answer is supported by indexed content. The endpoint returns citations and a grounding score, which apps use to gate publishing or display source links beside the answer. Critical for compliance-sensitive deployments.

Call groundingConfig:check with answer text 'Pricing is $99 per seat per month' and grounding sources set to data store ds-pricing, then return the grounding score and citations.

Custom Ranking Model Training

Train a custom search model on a data store via the trainCustomModel endpoint. The model learns from in-product engagement signals (clicks, dwell) and outranks the default for the customer's domain. Teams iterate by running listResults on evaluation jobs to measure NDCG and recall.

Trigger trainCustomModel on data store ds-products, then poll evaluation:listResults until the run is COMPLETED and return the NDCG@10 score.

Agent-Driven Search-and-Verify

Through Jentic, an AI agent can search a private data store for relevant context, then call groundingConfig:check to verify its synthesised answer is supported before responding to the user. Credentials are scoped per agent run by your Jentic One instance.

Use Jentic to search 'search a Vertex AI data store', load the schema, execute the search for query 'refund policy' on ds-help, then call groundingConfig:check on the synthesised answer.

Key Endpoints

75 endpoints — google discovery engine (the api behind vertex ai search and vertex ai conversation) lets developers build retrieval, search, and grounded conversational experiences over their own structured and unstructured data.

METHOD

PATH

DESCRIPTION

POST

/v1beta/{+completionConfig}:completeQuery

Get autocomplete suggestions

POST

/v1beta/{+completionConfig}:removeSuggestion

Remove an autocomplete suggestion

POST

/v1beta/{+groundingConfig}:check

Check whether an answer is grounded against sources

POST

/v1beta/{+dataStore}:trainCustomModel

Train a custom ranking model on a data store

POST

/v1beta/{+evaluation}:listResults

List results of a search-quality evaluation

POST

/v1beta/{+identityMappingStore}:importIdentityMappings

Import enterprise identity mappings

POST

/v1beta/{+completionConfig}:completeQuery

Get autocomplete suggestions

POST

/v1beta/{+completionConfig}:removeSuggestion

Remove an autocomplete suggestion

POST

/v1beta/{+groundingConfig}:check

Check whether an answer is grounded against sources

POST

/v1beta/{+dataStore}:trainCustomModel

Train a custom ranking model on a data store

POST

/v1beta/{+evaluation}:listResults

List results of a search-quality evaluation

Why Jentic?

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

Credential isolation

Your Google OAuth credential for Discovery Engine 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 'ground a response with Vertex AI Search' or 'autocomplete a search query', and Jentic returns the matching Discovery Engine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Discovery Engine API through Jentic.

What authentication does the Discovery Engine API use?

OAuth 2.0 with the cloud-platform scope. Through Jentic, OAuth tokens are scoped per agent run and stored encrypted in your Jentic One instance, so service-account JSON keys never enter the agent runtime.

Can I ground LLM answers against my own documents with Discovery Engine?

Yes. The /v1beta/{groundingConfig}:check endpoint takes an answer plus grounding sources (data stores or chunks) and returns a grounding score plus citations. Use it to gate publishing of LLM-generated content.

What are the rate limits for the Discovery Engine API?

Quotas are per project and depend on the operation: query and complete operations have higher per-second budgets than write or train operations. Check the Google Cloud Console under APIs and Services for the current quotas on your project.

How do I run autocomplete on a data store through Jentic?

Search 'autocomplete a Vertex AI Search query', load the schema for /v1beta/{completionConfig}:completeQuery, then execute it with your completion config name and input string. Jentic returns the suggestion list.

Does Discovery Engine support per-user ACLs?

Yes. Use identityMappingStore:importIdentityMappings to load enterprise identities, then queries scoped to a user respect document-level ACLs at search time. Useful for HR, legal, and finance content where access varies by role.

Is the Discovery Engine API free?

No. Pricing is per query and per indexed document, with tiers for Search, Recommendations, and Conversation. Custom model training has separate compute charges. Check current pricing in the Google Cloud Console.

Can I limit what my agent is allowed to do with the Discovery Engine API?

Yes. Because Discovery Engine puts the resource name in the URL path, such as {+dataStore} and {+servingConfig}, your self-hosted Jentic One instance lets you write rules that pin the agent to a single data store or serving config, so it can complete queries and run groundingConfig:check there and nothing else. You decide which operations the agent may call, so state-changing ones like trainCustomModel or importIdentityMappings stay out of reach unless you add them. The OAuth credential is held by your own instance and injected at execution time, so the agent only ever exercises the access you granted.

Google Discovery Engine API

Connect the Discovery Engine API to your agent

Capabilities

Start building with Discovery Engine API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs