Google Digital Asset Links API

Name: Digital Asset Links API
Brand: Digital Asset Links API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationnone3 Endpoints

Install Jentic One Beta

Connect the Digital Asset Links API to your agent

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

Check whether a source website has authorized a target Android app for a given relation

Bulk-check multiple asset link statements in one request

List all statements published by a source asset

GET STARTED

Start building with Digital Asset Links API

Explore with Jentic

View OpenAPI Document

For Agents

Verify ownership and trust relationships between websites and Android apps so platforms can grant cross-asset capabilities.

Use for: Check whether example.com has authorized my Android app for App Links, Verify the asset links statement on a website, List all digital asset link statements for a domain, Bulk check multiple asset link relations in one call

Not supported: Does not handle iOS Universal Links, runtime device attestation, or in-app authentication - use for declarative website-to-Android-app trust verification only.

Google Digital Asset Links lets web and mobile owners declare verifiable relationships between online assets - for example, that an Android app is the official companion to a website. Apps and platforms use the API to check whether a given source asset (a website) has authorized a target asset (an Android app) for actions like Smart Lock for Passwords, App Links, and Chrome Custom Tabs verification. The lookups are unauthenticated GETs over public statement files (assetlinks.json) hosted on the source asset.

Use Cases

Patterns agents use Digital Asset Links API for, with concrete tasks.

★ Android App Links Verification

Mobile teams use the assetlinks:check endpoint to confirm that the assetlinks.json hosted at a domain authorizes their app's package name and signing certificate for the delegate_permission/common.handle_all_urls relation. This is the same check Android performs at install time - running it in CI catches misconfigured asset link files before release.

Call assetlinks:check with source website https://example.com, target android_app com.example.app with sha256_cert_fingerprint, and relation delegate_permission/common.handle_all_urls.

Smart Lock Credential Sharing Audit

Identity teams use bulkCheck to audit which apps are entitled to share credentials with a website via the delegate_permission/common.get_login_creds relation. Running this nightly surfaces accidental authorizations or removed apps, supporting password-manager and SSO compliance.

Call assetlinks:bulkCheck with three target Android apps and the get_login_creds relation against source https://example.com, then return only those that fail the check.

Statement Discovery and Reporting

Use statements:list to enumerate every relation a source asset has declared. Useful for security reviews of acquired domains - surface every Android app, iOS bundle, or web origin a domain currently trusts, and feed the list into change-management.

Call statements:list for source https://example.com and return every target asset and relation declared in its assetlinks.json.

Agent-Driven App Trust Verification

Through Jentic, an AI agent verifies whether a website trusts a candidate Android app before recommending an integration path. The agent calls assetlinks:check with the package name and certificate fingerprint, returning a clean verified or not-verified outcome to the user without needing OAuth credentials (this API requires none).

Use Jentic to search 'check digital asset link', load the assetlinks:check schema, and execute it for source https://acme.com and target Android app com.acme.checkout.

Key Endpoints

3 endpoints — google digital asset links lets web and mobile owners declare verifiable relationships between online assets - for example, that an android app is the official companion to a website.

METHOD

PATH

DESCRIPTION

GET

/v1/assetlinks:check

Check a single asset link statement

POST

/v1/assetlinks:bulkCheck

Check multiple asset link statements in one call

GET

/v1/statements:list

List all statements published by a source asset

GET

/v1/assetlinks:check

Check a single asset link statement

POST

/v1/assetlinks:bulkCheck

Check multiple asset link statements in one call

GET

/v1/statements:list

List all statements published by a source asset

Why Jentic?

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

Credential isolation

The Digital Asset Links API needs no credential, so there is nothing to store. Requests run through your own Jentic One instance, and no secret enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'verify a website-to-app link' or 'list asset link statements', and Jentic returns the matching Digital Asset Links 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 Digital Asset Links API through Jentic.

What authentication does the Digital Asset Links API use?

None. The check, bulkCheck, and list endpoints are unauthenticated GETs that read public assetlinks.json files hosted by source assets. Through Jentic, no credentials are needed and nothing sensitive is exchanged.

Can I check Android App Links with this API?

Yes. Call /v1/assetlinks:check with the source web asset, target android_app (package_name plus sha256_cert_fingerprints), and relation delegate_permission/common.handle_all_urls - this is the same verification Android performs at install time.

What are the rate limits for the Digital Asset Links API?

Google publishes a default of around 10,000 requests per day per project for this API, with no documented per-second cap. Quota can be raised in the Google Cloud Console if your verification volume exceeds the default.

How do I list all statements for a domain through Jentic?

Search 'list digital asset link statements', load the schema for /v1/statements:list, then execute it with source.web.site set to https://example.com. Jentic returns the parsed statement list.

Does the Digital Asset Links API support iOS app verification?

The statement model supports web and android_app target asset types but does not validate iOS Universal Links - Apple uses its own apple-app-site-association format. Use this API for Android and web cross-asset trust only.

Why does my check fail when the assetlinks.json looks correct?

Common causes: missing or misordered SHA-256 cert fingerprints (must match the signing cert exactly, uppercase hex with colons), incorrect Content-Type on the file (must be application/json), or HTTP redirects on the .well-known path. Fix the source file and retry the check.

Google Digital Asset Links API

Connect the Digital Asset Links API to your agent

Capabilities

Start building with Digital Asset Links API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs