Slite
Slite is a collaborative documentation and knowledge base platform with a REST API for managing notes, channels, documents, templates, and team knowledge bases. It enables asynchronous work through AI-powered search, document creation, and automated knowledge management workflows. The Slite Public API provides programmatic access to workspaces using Bearer token authentication and follows the OpenAPI v3.0 standard.
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 Slite the way a machine reads it — 74 machine-readable artifacts across 7 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 — Slite scores 50.8/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Slite
Each block below is one kind of artifact we hold for Slite. 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 7
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.
Slite Ask API
The Ask API from Slite — 2 operation(s) for ask.
Slite Groups API
The Groups API from Slite — 2 operation(s) for groups.
Slite Knowledge Management API
The Knowledge Management API from Slite — 4 operation(s) for knowledge management.
Slite Me API
The Me API from Slite — 1 operation(s) for me.
Slite Notes API
The Notes API from Slite — 8 operation(s) for notes.
Slite Search Notes API
The Search Notes API from Slite — 1 operation(s) for search notes.
Slite Users API
The Users API from Slite — 2 operation(s) for users.
Scroll within the panel for all 7 ·
Pricing 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.
Slite 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.
Slite 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.
Slite Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Api Context
JSON-LDcontext Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Slite API Rules
SPECTRALJSON Schema 39
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AnswerAndSources
JSON SCHEMAAskDisabledError
JSON SCHEMAAskQuotaExceededError
JSON SCHEMAAskRateLimitedError
JSON SCHEMADeletedNoteResult
JSON SCHEMAExportedNote
JSON SCHEMAFieldErrors
JSON SCHEMAGroup
JSON SCHEMAHtml
JSON SCHEMAKnowledgeManagementFirst
JSON SCHEMAListHitsPerPage
JSON SCHEMAListNotesOrderBy
JSON SCHEMAListPage
JSON SCHEMAListResult
JSON SCHEMAMarkdown
JSON SCHEMAMe
JSON SCHEMANote
JSON SCHEMANoteContentFormat
JSON SCHEMANoteOwner
JSON SCHEMANoteWithContent
JSON SCHEMAObjectType
JSON SCHEMAPaginatedGroups
JSON SCHEMAPaginatedNotes
JSON SCHEMAPaginatedUsers
JSON SCHEMAPublicApiAuthError
JSON SCHEMAPublicApiDisabledError
JSON SCHEMAPublicApiError
JSON SCHEMAPublicApiFieldValidationError
JSON SCHEMAPublicApiNotFoundError
JSON SCHEMAPublicApiRateLimitError
JSON SCHEMAPublicApiReviewState
JSON SCHEMARecord_string.unknown_
JSON SCHEMASearchNoteHit
JSON SCHEMASearchNoteHitsPerPage
JSON SCHEMASearchNotePage
JSON SCHEMASearchNoteResult
JSON SCHEMASearchNoteType
JSON SCHEMASource
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 39 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Ask
EXAMPLECreatenote
EXAMPLEDelete Index
EXAMPLEFlagnoteasoutdated
EXAMPLEGetgroupbyid
EXAMPLEGetnotebyid
EXAMPLEGetnotechildren
EXAMPLEGetuserbyid
EXAMPLEIndex
EXAMPLEList Index
EXAMPLEListnotes
EXAMPLEMe
EXAMPLESearchgroups
EXAMPLESearchnotes
EXAMPLESearchusers
EXAMPLEUpdatenote
EXAMPLEUpdatenotearchivedstate
EXAMPLEUpdatenoteowner
EXAMPLEVerifynote
EXAMPLEScroll within the panel for all 19 ·
Security 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 Slite — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/slite · machine-readable index on apis.io