The Guardian Content API
✓ Official Vendor SpecCRMCustomer SupportapiKey5 EndpointsREST
For Agents
Programmatically search for content, get a single content item. Covers 5 operations with apiKey authentication.
Use for: I need to for content, I want to a single content item, Search for for tags, Find all all sections
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
The Guardian's Open Platform Content API provides free access to all content published on theguardian.com. Search for articles, browse sections and tags, retrieve specific content items, and access edition-specific content. Supports filtering by date, section, tag, and more. The API exposes 5 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the The Guardian Content API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Guardian 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftheguardian.com%2Ftheguardian" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftheguardian.com%2Ftheguardian" | 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.
Capabilities
What an agent can do with The Guardian Content API.
Search for content
Get a single content item
List all sections
Query and filter The Guardian Content API records by parameters
Monitor The Guardian Content API operational status and events
Use Cases
Patterns agents use The Guardian Content API for, with concrete tasks.
★ CRM Operations
Use the The Guardian Content API to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including search for content, get a single content item, search for tags.
Call GET /search to search for content
Automated Content Management
Automate content operations by combining multiple The Guardian Content API endpoints. Agents can get a single content item and then search for tags in a single workflow.
Call GET /{contentId} to get a single content item, then verify the result
AI Agent Integration via Jentic
AI agents discover and call The Guardian Content API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'search for content', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
5 endpoints — the guardian's open platform content api provides free access to all content published on theguardian.
METHOD
PATH
DESCRIPTION
GET
/search
Search for content
GET
/{contentId}
Get a single content item
GET
/tags
Search for tags
GET
/sections
List all sections
GET
/editions
List all editions
GET
/search
Search for content
GET
/{contentId}
Get a single content item
GET
/tags
Search for tags
GET
/sections
List all sections
GET
/editions
List all editions
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring The Guardian Content API by hand means passing your API key against content.guardianapis.com and handling each search and content endpoint yourself. Through Jentic you install once, import The Guardian Content API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Guardian Content API is read-only and puts the content id in the URL path (/{contentId}), so a rule can pin your agent to reading one item. You choose the operations it may call, so it only reaches the endpoints you include, such as search or fetching a single article.
Credential isolation
Your Guardian API key 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 'search for articles on a topic' or 'list content tags', and Jentic returns the matching Guardian operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using The Guardian Content API through Jentic.
What authentication does the The Guardian Content API use?
The The Guardian Content API uses an API key passed in the `api-key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I search for content with the The Guardian Content API?
Yes. Use the GET /search endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the The Guardian Content API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I search for content through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for content'. Jentic returns the matching The Guardian Content API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the The Guardian Content API have?
The The Guardian Content API exposes 5 endpoints covering content, tags, sections operations.
Can I limit what my agent is allowed to do with the Guardian Content API?
Yes. Because Jentic One is self-hosted, your own rules decide which Guardian operations the agent may call, so you can allow only GET /search and GET /{contentId} while blocking the rest. Since the API is read-only and puts the content id in the URL path, you can pin the agent to fetching a single article or restrict it to searching by section or tag. Your Guardian API key stays with your instance and is injected only when an allowed operation runs.
GET STARTED