Fact Check Tools API

Name: Fact Check Tools API API
Brand: Fact Check Tools API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData Transformationoauth27 EndpointsREST

For Agents

Search Google's index of fact checks by claim text or image, and manage publisher ClaimReview pages so they appear in Google's fact-check surfaces.

Quickstart

Get started with Fact Check Tools 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 published fact checks for a claim"

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

Capabilities

What an agent can do with Fact Check Tools API API.

Search published fact checks by free-text claim and language to find existing reviews from Google's indexed publishers

Search fact checks for an image by URL to surface visual claim reviews

Create a publisher ClaimReview page with one or more claim reviews so Google can index it

List the publisher's existing ClaimReview pages with paging and filtering

GET STARTED

Start building with Fact Check Tools API API

Explore with Jentic

View OpenAPI Document

Use for: Search whether a given claim has already been fact-checked by anyone, Find fact checks for an image URL circulating on social media, I need to create a ClaimReview page for an article I published, List all ClaimReview pages my publisher has registered

Not supported: Does not assess claim truthfulness directly, host original articles, or moderate user-generated content — use for searching ClaimReview-marked fact checks and managing publisher pages only.

The Fact Check Tools API exposes Google's index of ClaimReview-marked-up fact checks published across the open web. Developers can search published fact checks by claim text, by image, or by topic, and publishers can manage their own ClaimReview pages programmatically — creating, listing, updating, and deleting page entries that Google ingests into the index. The API is the canonical interface for both consuming third-party fact-check signals and contributing publisher claim reviews.

Use Cases

Patterns agents use Fact Check Tools API API for, with concrete tasks.

★ Newsroom Claim Triage

Newsroom researchers and fact-checking teams query the Fact Check Tools API to see whether a circulating claim has already been reviewed by a peer organisation before they spend time on a fresh check. The claims:search endpoint returns ClaimReview metadata including the rating, the review URL, and the publisher, letting researchers cite the existing review or differentiate their angle. This shaves hours off triage during fast-moving stories.

Call GET /v1alpha1/claims:search with query='5g causes covid' and languageCode='en' and return the top three publishers, ratings, and URLs.

Visual Misinformation Detection

Trust and safety teams reviewing image-based misinformation use claims:imageSearch to find published fact checks tied to specific images circulating online. The API returns ClaimReviews that reference the image, including the review's textual rating, helping moderation pipelines surface authoritative context to users.

Call GET /v1alpha1/claims:imageSearch with imageUri set to the questionable image URL and surface any matching ClaimReview entries to the moderator.

Publisher ClaimReview Distribution

Fact-checking publishers publish ClaimReview-tagged articles and use the API to register, list, and maintain those pages so Google's fact-check surfaces (Search, News, YouTube info panels) ingest them quickly and reliably. The same flow keeps stale or retracted pages out of the index when articles are taken down.

POST /v1alpha1/pages with the article URL, publishing date, and claimReviewMarkups list, then list and verify the page appears in the publisher's pages collection.

Agent-Mediated Claim Verification via Jentic

An AI agent answering a user question that depends on a contested claim can call the Fact Check Tools API through Jentic to surface authoritative existing reviews before responding. The agent does not need to learn the claims:search or claims:imageSearch endpoint shapes; Jentic returns the matching operation with its query parameters per intent.

Search Jentic for 'check if a claim has been fact-checked', load the GET /v1alpha1/claims:search schema, and execute it with the claim text before composing the answer.

Key Endpoints

7 endpoints — the fact check tools api exposes google's index of claimreview-marked-up fact checks published across the open web.

METHOD

PATH

DESCRIPTION

GET

/v1alpha1/claims:search

Search fact checks by claim text

GET

/v1alpha1/claims:imageSearch

Search fact checks by image URL

GET

/v1alpha1/pages

List publisher ClaimReview pages

POST

/v1alpha1/pages

Create a ClaimReview page

GET

/v1alpha1/{+name}

Get a single ClaimReview page

PUT

/v1alpha1/{+name}

Update a ClaimReview page

DELETE

/v1alpha1/{+name}

Delete a ClaimReview page

GET

/v1alpha1/claims:search

Search fact checks by claim text

GET

/v1alpha1/claims:imageSearch

Search fact checks by image URL

GET

/v1alpha1/pages

List publisher ClaimReview pages

POST

/v1alpha1/pages

Create a ClaimReview page

GET

/v1alpha1/{+name}

Get a single ClaimReview page

Why though Jentic?

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

Credential isolation

OAuth refresh tokens (and API keys for unauthenticated search) are stored encrypted in the Jentic vault. Agents only see scoped Bearer tokens, so publisher-side write operations cannot be replayed if an agent context is leaked.

Intent-based discovery

Agents search by intent (e.g. 'has this claim been fact-checked') and Jentic returns the right claims:search or claims:imageSearch operation with its query parameters and pagination, so the agent does not have to learn the v1alpha1 path conventions.

Time to first call

Direct Fact Check Tools integration: 0.5-1 day for OAuth, query parameters, and pagination. Through Jentic: under 30 minutes for a claim-verification step in an agent.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Custom Search API

Web search to find articles around a claim before checking against the fact-check index

Use to surface candidate articles that may need fact-check verification

Complementary

Search Console API

Verifies publisher domain ownership for ClaimReview submission

Use when onboarding a new publisher domain to Fact Check Tools

Alternative

Books API

Authoritative reference data for verifying claims about published books

Choose Books when the claim concerns a publication's content rather than an indexed news fact check

FAQs

Specific to using Fact Check Tools API API through Jentic.

What authentication does the Fact Check Tools API use?

The Fact Check Tools API uses Google OAuth 2.0 with the userinfo.email scope. Search endpoints accept user OAuth tokens or API keys depending on quota; publisher endpoints require an OAuth token issued to a verified publisher account. Through Jentic the credentials live in the encrypted vault.

Can I search for fact checks about a specific image?

Yes. GET /v1alpha1/claims:imageSearch accepts an imageUri query parameter and returns ClaimReview entries that reference that image, including the review URL and rating. This is useful for visual misinformation triage.

What are the rate limits for the Fact Check Tools API?

The API enforces standard Google per-project quotas in the Cloud Console (typical default 600 read requests per minute). Search results are bounded per call and pageToken-paginated; publisher endpoints are scoped to the publisher's verified domain.

How do I publish a ClaimReview page through Jentic?

Search Jentic for 'publish a ClaimReview page', load the POST /v1alpha1/pages schema, and execute it with the page URL and claimReviewMarkups list. The publisher account must be verified in the Fact Check Tools console first.

Is the Fact Check Tools API free?

Yes. The API is free for both search and publisher operations within standard quota limits. There is no per-call charge for either consuming fact checks or registering publisher ClaimReview pages.

How do I find fact checks in a specific language?

Pass the languageCode query parameter to GET /v1alpha1/claims:search (e.g. 'en', 'es', 'pt') to restrict results to ClaimReviews in that language. Combine with reviewPublisherSiteFilter to scope results to specific publishers.