Glean
Glean is an AI-powered work assistant and enterprise search platform that connects to a company's apps and data sources to provide unified search, generative answers, and autonomous agents grounded in enterprise knowledge. Glean exposes a Client API for end-user features (search, chat, agents, answers), an Indexing API for ingesting custom data sources, and Admin and Activity APIs for governance and observability.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Glean the way a machine reads it — 31 machine-readable artifacts across 22 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Glean scores 50.6/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Glean
Each block below is one kind of artifact we hold for Glean. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Glean Search API
Run unified semantic and keyword search across all connected enterprise content with permission-aware results, filters, and facets.
Glean Chat API
Multi-turn generative chat over enterprise content with grounded answers, citations, and tool use.
Glean Agents API
Build and invoke autonomous agents that reason over enterprise data and perform multi-step workflows on behalf of users.
Glean People API
Look up people in the enterprise knowledge graph including profile, expertise, org chart relationships, and activity.
Glean Activity API
Read and submit activity signals (views, clicks, edits) that improve personalization and ranking across the Glean instance.
Glean Governance API
Administer governance policies, data classification, and access controls across the Glean instance.
Glean activity API
The activity API from Glean — 2 operation(s) for activity.
Glean agents API
The agents API from Glean — 5 operation(s) for agents.
Glean announcements API
The announcements API from Glean — 3 operation(s) for announcements.
Glean answers API
The answers API from Glean — 5 operation(s) for answers.
Glean chat API
The chat API from Glean — 8 operation(s) for chat.
Glean collections API
The collections API from Glean — 8 operation(s) for collections.
Glean documents API
The documents API from Glean — 3 operation(s) for documents.
Glean governance API
The governance API from Glean — 3 operation(s) for governance.
Glean insights API
The insights API from Glean — 1 operation(s) for insights.
Glean people API
The people API from Glean — 2 operation(s) for people.
Glean pins API
The pins API from Glean — 5 operation(s) for pins.
Glean search API
The search API from Glean — 5 operation(s) for search.
Glean shortcuts API
The shortcuts API from Glean — 5 operation(s) for shortcuts.
Glean summarize API
The summarize API from Glean — 1 operation(s) for summarize.
Glean tools API
The tools API from Glean — 2 operation(s) for tools.
Glean verification API
The verification API from Glean — 3 operation(s) for verification.
Scroll within the panel for all 22 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Glean Client REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Glean Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Glean Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Glean Finops
FINOPSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Glean — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/glean · machine-readable index on apis.io