Prismic Content API

Name: Prismic Content API
Brand: Prismic Content API
Availability: InStock

✓ Official Vendor SpecMarketingContent ManagementapiKey2 EndpointsREST

For Agents

Query and retrieve structured content from Prismic repositories using predicate-based search. Supports filtering by content type, tags, fulltext, date, and geographic proximity with CDN-backed delivery.

Install Jentic One Beta

Connect the Prismic Content API to your agent

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

Search documents using Prismic predicate queries with type, tag, UID, and fulltext filters

Resolve linked document fields inline using fetchLinks or GraphQuery parameters

Paginate through large content sets with page, pageSize, and cursor-based after parameter

GET STARTED

Start building with Prismic Content API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Prismic Content API for, with concrete tasks.

★ Headless CMS Content Delivery

Deliver structured content from Prismic to frontend applications, static site generators, or mobile apps. The search endpoint returns documents with their full data payloads, metadata, and publication timestamps. Content is served via CDN for low latency. Agents can fetch all documents of a given type (e.g., blog posts, product pages) or retrieve individual documents by UID for specific page rendering.

Query the Prismic API with ref set to the master ref and q set to '[[at(document.type,"blog_post")]]' with pageSize 10 and orderings '[my.blog_post.date desc]'

Multilingual Content Retrieval

Serve content in multiple languages from a single Prismic repository. The lang parameter filters results to a specific locale (e.g., 'en-us', 'fr-fr'), while each document includes alternate_languages references to its translations. This enables agents to fetch localized content for regional audiences or build language switchers that link to translated versions of the same document.

Fetch all documents of type 'page' in French (lang='fr-fr'), then for the first result, retrieve its English version using the alternate_languages ID

Content Search and Filtering

Search across repository content using Prismic's predicate query language. Predicates support exact match, exclusion, list membership, fulltext search, date comparisons, numeric ranges, and geographic proximity. Multiple predicates combine with AND logic. This enables building search interfaces, content recommendations, and filtered content feeds without a separate search service.

Search documents with predicates '[[fulltext(document,"machine learning")][at(document.type,"article")]]' and return the titles and publication dates of matching results

AI Agent Content Fetching via Jentic

AI agents can query Prismic content through Jentic to populate dynamic responses, fetch page content for rendering, or retrieve structured data for processing. Jentic provides the operation schema for the search endpoint including all predicate syntax options, so agents construct valid queries without memorizing Prismic's query language.

Search Jentic for 'search prismic documents', load the searchDocuments operation schema, and execute a query for all documents of type 'product' with fetch 'product.name,product.price'

Key Endpoints

2 endpoints — prismic content api delivers structured content from prismic repositories via a cdn-backed query interface.

METHOD

PATH

DESCRIPTION

GET

/api/v2

Get repository metadata, refs, languages, and content types

GET

/api/v2/documents/search

Search documents with predicate queries and pagination

GET

/api/v2

Get repository metadata, refs, languages, and content types

GET

/api/v2/documents/search

Search documents with predicate queries and pagination

Why Jentic?

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

Credential isolation

Your Prismic access token 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 'fetch blog posts from Prismic' or 'search Prismic content by tag', and Jentic returns the searchDocuments operation with its input schema, including predicate syntax, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Prismic Content API through Jentic.

What authentication does the Prismic Content API use?

The Prismic Content API uses an access_token for private repositories, passed either as a query parameter or in the Authorization header as 'Token your-access-token'. Public repositories require no authentication. Through Jentic, access tokens are stored encrypted in the vault and agents authenticate without handling raw token values.

What are the rate limits for the Prismic Content API?

Prismic applies rate limiting and returns a 429 status code when exceeded. The CDN layer handles high read volumes efficiently, but burst traffic may trigger limits. Implement retry logic with backoff when you receive 429 responses. Content is served from CDN edge nodes for low latency reads.

How do I query documents by content type with the Prismic API?

Use the search endpoint GET /api/v2/documents/search with the ref parameter set to your master ref and q set to '[[at(document.type,"your_type")]]'. Replace 'your_type' with the API ID of your content type (e.g., 'blog_post', 'product'). Add pageSize and orderings parameters to control pagination and sort order.

Can I resolve linked document data inline with Prismic?

Yes. Use the fetchLinks parameter to specify which fields to resolve from linked documents (e.g., 'author.name,author.avatar'). For more complex nested data, use the graphQuery parameter which provides full control over field selection at multiple nesting levels. Both avoid separate API calls for linked content.

How do I fetch Prismic content for a specific language through Jentic?

Search Jentic for 'search prismic documents', load the searchDocuments operation schema, and execute with the lang parameter set to the locale code (e.g., 'fr-fr' for French). Use lang='*' to return all languages. Install with pip install jentic and set JENTIC_AGENT_API_KEY.

What query predicates does the Prismic Content API support?

The API supports predicates for exact match (at), exclusion (not), list membership (any, in), fulltext search (fulltext), field existence (has, missing), similarity (similar), geographic proximity (geopoint.near), numeric comparisons (number.lt, number.gt, number.inRange), and date comparisons (date.before, date.after, date.between). Combine multiple predicates in double brackets for AND logic.

Can I limit what my agent is allowed to do with the Prismic Content API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Prismic operations your agent may call and which credentials it may use. Prismic's delivery endpoints act on the repository and its search query rather than an ID in the URL path, so you scope the agent by operation: grant only the repository metadata read and the document search calls it needs. That keeps the agent limited to read-only content delivery, with no access to authoring, type definition, or media uploads.