Google Web Risk API

Name: Web Risk API
Brand: Web Risk API
Availability: InStock

✓ Official Vendor SpecSecurityThreat Detectionoauth28 EndpointsREST

Install Jentic One Beta

Connect the Web Risk API to your agent

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

Check a URL for phishing, malware, or unwanted-software classifications using uris:search

Compute privacy-preserving hash prefix diffs against threat lists with threatLists:computeDiff

Verify candidate hash prefixes locally and confirm full hashes via hashes:search

GET STARTED

Start building with Web Risk API

Explore with Jentic

View OpenAPI Document

For Agents

Check URLs against Google's threat lists for phishing, malware, and unwanted software, and submit suspicious URLs for review. Designed for moderation, link-shortening, and email security pipelines.

Use for: Check whether a URL is on Google's phishing list, Look up a domain in the malware threat list, Submit a phishing URL for review by Google, Retrieve full hashes that match a hash prefix from the local cache

Not supported: Does not handle vulnerability scanning of your own apps, bot detection, content moderation of text or images, or DNS filtering - use for URL threat lookups against Google's hosted threat lists only.

Use Cases

Patterns agents use Web Risk API for, with concrete tasks.

★ Link safety check before redirect

URL shorteners, email gateways, and chat platforms call uris:search before resolving a user-supplied link to block known phishing and malware destinations. The endpoint accepts a URL and a list of threat types and returns matched threats. Because Web Risk is paid and quota-managed, it suits high-traffic products that have outgrown the free Safe Browsing API.

Call GET /v1/uris:search with the URL https://example.com/login and threatTypes=MALWARE,SOCIAL_ENGINEERING and report whether any threat is returned.

Privacy-preserving local threat database

Browsers and security clients sync a local copy of Google's threat lists by calling threatLists:computeDiff and only requesting full hashes from hashes:search when a candidate prefix matches. This pattern keeps actual user URLs on the client and sends only truncated hashes upstream. Web Risk's diff format is identical in shape to Safe Browsing v4 so existing client logic ports cleanly.

Call GET /v1/threatLists:computeDiff with threatType=MALWARE and a stored versionToken, then update the local hash prefix database with the returned additions and removals.

Submitting newly discovered phishing URLs

Security teams that detect phishing pages targeting their brand submit those URLs to Google through POST /v1/{+parent}/submissions so that the entry can be added to threat lists and protect the wider Chrome and Android ecosystem. Submissions are processed as long-running operations; the operations endpoints track status. This is a useful integration for fraud and trust-and-safety workflows.

POST a submission with uri=https://fake-bank.example.com to /v1/projects/{project}/submissions and poll the returned operation until done is true.

Agent-driven URL screening through Jentic

Moderation and customer-support agents call Web Risk through Jentic to vet links before sending them to users or following them autonomously. The agent queries Jentic for check a url for phishing, loads the uris:search schema, and executes with the URL pulled from the conversation. Credential isolation in Jentic means OAuth tokens for the underlying Google project never enter the model's context.

Through Jentic, call GET /v1/uris:search with a URL extracted from a user message and threatTypes=MALWARE,SOCIAL_ENGINEERING,UNWANTED_SOFTWARE, then refuse to forward the link if any threat is returned.

Key Endpoints

8 endpoints — the google web risk api lets client applications check urls against google's continuously updated lists of unsafe web resources, including phishing pages, malware sites, and unwanted software.

METHOD

PATH

DESCRIPTION

GET

/v1/uris:search

Check a URL against threat lists

GET

/v1/hashes:search

Resolve hash prefixes to full hashes

GET

/v1/threatLists:computeDiff

Compute a diff of a threat list

POST

/v1/{+parent}/submissions

Submit a URL for review

GET

/v1/{+name}/operations

List long-running operations

POST

/v1/{+name}:cancel

Cancel a long-running operation

GET

/v1/uris:search

Check a URL against threat lists

GET

/v1/hashes:search

Resolve hash prefixes to full hashes

GET

/v1/threatLists:computeDiff

Compute a diff of a threat list

POST

/v1/{+parent}/submissions

Submit a URL for review

GET

/v1/{+name}/operations

List long-running operations

Why Jentic?

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

Credential isolation

Your Web Risk OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. Its refresh token never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check a URL for phishing' or 'look up a hash against threat lists', and Jentic returns the uris:search or submissions 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 Web Risk API through Jentic.

What authentication does the Web Risk API use?

Web Risk uses OAuth 2.0 (the Oauth2 and Oauth2c security schemes in the spec) scoped to https://www.googleapis.com/auth/cloud-platform. Through Jentic the OAuth credentials are stored in the encrypted vault and exchanged for short-lived access tokens at execution time.

How is Web Risk different from the free Safe Browsing API?

Web Risk is the paid commercial product with higher quotas, an SLA, and support for URL submissions through POST /v1/{+parent}/submissions. Safe Browsing v4 is free but rate limited and does not include the submission endpoint. The hash diff and lookup logic is otherwise compatible.

What are the rate limits for the Web Risk API?

Web Risk quotas are configured per Google Cloud project in the Cloud Console under APIs and Services and depend on your billing plan. Google publishes the contractual QPS in the Web Risk pricing documentation; for hash-based lookups the local cache built from threatLists:computeDiff handles the bulk of traffic so live calls stay well under quota.

How do I check a URL for phishing through Jentic?

Search Jentic for check a url for phishing, load the schema for GET /v1/uris:search, and execute it with the uri parameter and threatTypes including SOCIAL_ENGINEERING and MALWARE. Jentic returns the matched threats array; an empty response means the URL is not currently on a list.

Can I submit phishing URLs that target my brand?

Yes. POST /v1/{+parent}/submissions accepts a URI and creates a long-running operation. Track it through the operations endpoints (GET /v1/{+name}/operations or POST /v1/{+name}:cancel) until the operation completes. Approved submissions are added to Google's threat lists and propagate to Chrome and Android.

Can I limit what my agent is allowed to do with the Web Risk API?

Yes. Because Jentic One is self-hosted, you run your own instance and your own rules decide which Web Risk operations and which OAuth credential the agent may use. You can allow only read-only threat lookups such as GET /v1/uris:search and GET /v1/hashes:search while excluding the submission endpoint (POST /v1/{+parent}/submissions), so the agent can check URLs against Google's threat lists but cannot file new threat reports unless you explicitly add that operation. The OAuth credential is stored by your instance and injected at execution time, keeping it out of the agent's context.

Google Web Risk API

Connect the Web Risk API to your agent

Capabilities

Start building with Web Risk API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs