Google Abusive Experience Report API

Name: Abusive Experience Report API
Brand: Abusive Experience Report API
Availability: InStock

✓ Official Vendor SpecSecurityComplianceoauth22 Endpoints

Install Jentic One Beta

Connect the Abusive Experience Report API to your agent

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

Read the abusive experience status for a specific site as currently scored by Google

List every site that is failing the Abusive Experience Report at the time of the call

Surface the report URL where a site owner can review violations and request re-review

GET STARTED

Start building with Abusive Experience Report API

Explore with Jentic

View OpenAPI Document

For Agents

Check whether a site is failing Google's Abusive Experience Report and list all currently violating domains, so an agent can flag sites at risk of Chrome ad filtering.

Use for: Check whether example.com is failing the Abusive Experience Report, List all sites currently violating the Abusive Experience Report, Find the Google review URL for a site flagged for abusive experiences, Get the latest abusive experience status for a publisher domain

Not supported: Does not handle ad creative review, content moderation, or Chrome enforcement actions - use for reading abusive experience status on publisher sites only.

Use Cases

Patterns agents use Abusive Experience Report API for, with concrete tasks.

★ Publisher Compliance Monitoring

An ad operations team checks the Abusive Experience Report status of every domain in its portfolio on a daily schedule. The siteSummary endpoint returns the abusive status for a single site, and a Failing result triggers an internal ticket so the team can investigate the offending creatives before Chrome begins filtering ads on that domain.

For each domain in the portfolio list, call sites.get and emit a ticket whenever the abusiveStatus changes from PASSING to FAILING.

Industry-wide Abuse Tracking

A research team pulls the full list of sites currently failing the Abusive Experience Report to study trends in deceptive advertising. The violatingSites.list endpoint returns every flagged domain in a single call, which the team joins with traffic and category data to produce an industry report.

Call violatingSites.list, store the returned domains in a database, and compute the count of newly flagged sites since the previous run.

AI Agent Ad Quality Triage

An AI agent embedded in an ad-ops console uses Jentic to call the Abusive Experience Report API whenever a publisher onboards a new domain. The agent returns the current status, the report review URL, and a recommendation for whether the domain is safe to monetise immediately.

Given a new publisher domain, call sites.get and reply with the abusiveStatus, the reportUrl, and a one-line recommendation.

Key Endpoints

2 endpoints — the abusive experience report api exposes google's findings on sites that show abusive experiences such as fake messages, deceptive ads, and unexpected redirects.

METHOD

PATH

DESCRIPTION

GET

/v1/violatingSites

List all sites failing the Abusive Experience Report

GET

/v1/{+name}

Get the abusive experience status for a single site

GET

/v1/violatingSites

List all sites failing the Abusive Experience Report

GET

/v1/{+name}

Get the abusive experience status for a single site

Why Jentic?

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

Credential isolation

Your Google refresh token is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived access token at execution time. The refresh token never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check a site's abusive experience status', and Jentic returns the matching sites.get or violatingSites.list operation with its input schema so the agent calls the right endpoint without reading the reference.

Time to first call

FAQs

Specific to using Abusive Experience Report API through Jentic.

What authentication does the Abusive Experience Report API use?

It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/xapi.zoo scope. The site owner must have verified the property in Search Console under the same Google account. Jentic stores the refresh token in its encrypted vault and exchanges it for short-lived access tokens at request time.

Can I check a site I do not own with the Abusive Experience Report API?

The sites.get endpoint requires that the calling Google account is a verified owner of the site in Search Console. You can call violatingSites.list to read the full set of flagged domains regardless of ownership, but per-site detail is restricted to verified owners.

What are the rate limits for the Abusive Experience Report API?

Google does not publish a hard quota for this API and traffic is shared with the Search Console quota pool. In practice, polling sites.get more than once per minute per domain returns stale data because the underlying review cycle runs daily, so caching results for an hour is sufficient.

How do I list all violating sites through Jentic?

Run jentic search 'list violating sites in abusive experience report', load the returned operation, and execute it. The agent receives a typed response containing every domain currently flagged, with siteUrl, abusiveStatus, and the reportUrl for review.

Is the Abusive Experience Report API free?

Yes. The API is free to use under Google's standard API terms - there is no per-call charge. Quota usage counts against the project's shared Google APIs quota pool.

Can I limit what my agent is allowed to do with the Abusive Experience Report API?

Yes. Because Jentic One is self-hosted, your own rules decide which of this API's two read operations the agent may call and which credentials it may use. This API has no write operations, so you can allow the agent to list all violating sites, restrict it to reading a single named site's status, or permit both.