Overview
Glean
Glean Documentation
Content and agent signals
For agents (AI-generated): Glean developer documentation covering its Client and Agent APIs, OAuth, agent creation and runs, LLM model hub and admin console for enterprise AI search.
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-11-20T04:19:46.739Z. Cached copy · Source on glean.com
# Glean
> Glean Documentation
- [Glean](/index.md)
## tags
- [Tags](/tags.md)
### beta
- [One doc tagged with "Beta"](/tags/beta.md)
## administration
### about
The Admin console is where all enterprise-wide configuration for the Glean platform occurs.
- [About the Admin console](/administration/about.md): The Admin console is where all enterprise-wide configuration for the Glean platform occurs.
### actions
- [OAuth options for tools](/administration/actions/setup-actions/choose-central-or-custom-oauth.md): Choose between central OAuth and custom OAuth for OAuth-based tools, review connector support, and understand default token lifetimes.
### agent-identity
- [Set up Atlassian service credential](/administration/agent-identity/atlassian.md): Configure an Atlassian service-account API key so Glean agents can interact with Jira and Confluence through Atlassian's hosted MCP server under a non-human identity.
- [Set up AWS CloudWatch Logs service credential](/administration/agent-identity/aws-cloudwatch.md): Configure cross-account IAM role assumption with Workload Identity Federation so Glean agents can read AWS CloudWatch Logs.
- [Set up Coda service credential](/administration/agent-identity/coda.md): Configure a dedicated Coda identity and MCP-restricted API token so Glean agents can work with approved Coda content.
- [Set up Cursor service credential](/administration/agent-identity/cursor.md): Configure a Cursor API key so Glean agents can launch and monitor Cursor Cloud Agents that work on your repositories and open pull requests.
- [Set up Datadog service credential](/administration/agent-identity/datadog.md): Configure Datadog API and Application keys so Glean agents can query logs, metrics, traces, monitors, and dashboards through Datadog's remote MCP server under a service account.
- [Set up GCP BigQuery service credential](/administration/agent-identity/gcp-bigquery.md): Configure GCP service account impersonation so Glean agents can query BigQuery datasets.
- [Set up GCP Cloud Run Jobs service credential](/administration/agent-identity/gcp-cloud-run-jobs.md): Configure a GCP service credential so Glean agents can start existing Cloud Run jobs and monitor executions.
- [Set up GCP cloud logging service credential](/administration/agent-identity/gcp-service-account.md): Configure GCP service account impersonation and register it as a service credential in Glean so agents can call GCP APIs.
- [Set up GCP Storage service credential](/administration/agent-identity/gcp-storage.md): Configure GCP service account impersonation for agent access to Cloud Storage buckets and objects.
- [Set up GitHub service credential](/administration/agent-identity/github-app.md): Let Glean agents read GitHub repository data using a GitHub app.
- [Set up GitLab service credential](/administration/agent-identity/gitlab.md): Configure a GitLab service account and access token so Glean agents can work with approved GitLab projects.
- [Set up Gong ser
…
Published headings
The index marks this publisher’s heading coverage as partial.
183 indexed headings in this publisher record.
Show all 183 indexed headings
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=glean.com · GET /v1/domain/glean.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.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage glean.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for glean.com:
1. POST https://agentwebmap.com/v1/sites/glean.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://glean.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/glean.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/glean.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.