Guru
Guru is an AI-powered knowledge management and enterprise search platform that captures company knowledge into verifiable cards organized into collections, surfaces answers directly inside the apps employees already use (Slack, Chrome, Microsoft Teams, Salesforce), and uses AI to keep content trusted and up to date. The Guru REST API provides programmatic access to cards, collections, boards, users, groups, tags, analytics, and verifications. Authentication uses HTTP Basic Auth with a user token or Collection token generated by a Guru admin.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Guru the way a machine reads it — 22 machine-readable artifacts across 18 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 — Guru scores 32.1/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). 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 Guru
Each block below is one kind of artifact we hold for Guru. 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 18
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.
Guru REST API
REST API for managing cards, collections, boards, board sections, folders, users, groups, tags, webhooks, analytics, and card verifications in Guru. Authentication uses HTTP Bas...
Guru Analytics API
The Analytics API from Guru — 2 operation(s) for analytics.
Guru Announcements API
The Announcements API from Guru — 8 operation(s) for announcements.
Guru Answers API
The Answers API from Guru — 3 operation(s) for answers.
Guru CardComments API
The CardComments API from Guru — 2 operation(s) for cardcomments.
Guru Cards API
The Cards API from Guru — 8 operation(s) for cards.
Guru CardVerifiers API
The CardVerifiers API from Guru — 3 operation(s) for cardverifiers.
Guru Collections API
The Collections API from Guru — 3 operation(s) for collections.
Guru Folders API
The Folders API from Guru — 10 operation(s) for folders.
Guru Groups API
The Groups API from Guru — 5 operation(s) for groups.
Guru Members API
The Members API from Guru — 1 operation(s) for members.
Guru People API
The People API from Guru — 3 operation(s) for people.
Guru Search API
The Search API from Guru — 4 operation(s) for search.
Guru Tags API
The Tags API from Guru — 8 operation(s) for tags.
Guru Tasks API
The Tasks API from Guru — 1 operation(s) for tasks.
Guru Templates API
The Templates API from Guru — 5 operation(s) for templates.
Guru TicketLinking API
The TicketLinking API from Guru — 5 operation(s) for ticketlinking.
Guru User API
The User API from Guru — 1 operation(s) for user.
Scroll within the panel for all 18 ·
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).
Guru API
OPEN COLLECTIONSecurity Posture 2
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 Guru — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/guru · machine-readable index on apis.io