chrome.com valid

Documentation

Code samples, guides, and API reference you need for whatever you're building.

For agents: Chrome developer documentation: code samples, guides and API reference, especially built-in client-side AI APIs and on-device model caching for web apps.

chromebuilt-in aiweb apisclient-side aibrowser developmentmodel caching

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T01:05:31.802Z. Cached copy · Source on chrome.com

# Documentation

Code samples, guides, and API reference you need for whatever you're building.

## Docs

- [Documentation](https://developer.chrome.com/docs.md.txt): Code samples, guides, and API reference you need for whatever you're building.
- [Accessibility](https://developer.chrome.com/docs/accessibility.md.txt)
- [Artificial Intelligence in Chrome](https://developer.chrome.com/docs/ai.md.txt): Learn about building with client-side AI in Chrome.
- [Built-in AI](https://developer.chrome.com/docs/ai/built-in.md.txt): Learn about AI on the web with Chrome.
- [Built-in AI APIs](https://developer.chrome.com/docs/ai/built-in-apis.md.txt): Built-in AI is the latest offering for bringing powerful models to users, while protecting sensitive data and improving latency.
- [Cache models in the browser](https://developer.chrome.com/docs/ai/cache-models.md.txt): To make future launches of your AI-powered applications faster, explicitly cache the model data on-device.
- [When to choose client-side AI](https://developer.chrome.com/docs/ai/client-side.md.txt): Client-side AI brings powerful models to users, while protecting sensitive data and improving latency.
- [Debug Gemini Nano](https://developer.chrome.com/docs/ai/debug-gemini-nano.md.txt): There's a special Chrome-internal page to see details on prompts to Gemini Nano. This guide explains how make use of it for debugging.
- [Evaluate product reviews with AI](https://developer.chrome.com/docs/ai/evaluate-reviews.md.txt): Client-side AI is the latest offering for bringing powerful models to users, while protecting sensitive data and improving latency.
- [Hybrid AI prompting with Firebase AI Logic](https://developer.chrome.com/docs/ai/firebase-ai-logic.md.txt): Use Firebase AI Logic with your AI apps for a cloud fallback if built-in AI APIs aren't supported.
- [Get started with built-in AI](https://developer.chrome.com/docs/ai/get-started.md.txt): Learn the requirements to start building features and applications with built-in AI.
- [What is artificial intelligence?](https://developer.chrome.com/docs/ai/glossary.md.txt): Understand the difference between built-in AI, client-side AI, and server-side AI, and so much more.
- [Inform users of model download](https://developer.chrome.com/docs/ai/inform-users-of-model-download.md.txt): This guide explains how to improve the user experience while waiting for built-in AI models and their customizations to download, extract, and load into memory, offering both client-side only and hybrid implementation strategies.
- [Join the early preview program](https://developer.chrome.com/docs/ai/join-epp.md.txt): Sign up for the early preview program.
- [Thanks for signing up to the EPP](https://developer.chrome.com/docs/ai/join-epp/success.md.txt): Thanks for joining the built-in AI early preview program.
- [Language detection with built-in AI](https://developer.chrome.com/docs/ai/language-detection.md.txt): The Language Detector API offers built-in language discov
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=chrome.com · GET /v1/domain/chrome.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for chrome.com:
1. POST https://agentwebmap.com/v1/sites/chrome.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://chrome.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/chrome.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/chrome.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.