Typesense
Typesense is a fast, typo-tolerant, open-source search engine designed for developer productivity. It provides instant search experiences with support for full-text search, faceting, filtering, sorting, geo-based search, vector search, and conversational AI search. Typesense is available as an open-source self-hosted solution or as a managed cloud service via Typesense Cloud.
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 Typesense the way a machine reads it — 132 machine-readable artifacts across 2 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 — Typesense scores 42.1/100 (developing), with a separate agent-readiness read of 22/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Typesense's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/typesense/"
title="Typesense on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/typesense.svg"
alt="Typesense Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/typesense/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/typesense/"
title="Typesense on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/typesense/card.svg"
alt="Typesense Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Typesense
Each block below is one kind of artifact we hold for Typesense. 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 6
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.
Typesense Analytics Events API
Log and retrieve user interaction events such as clicks, conversions, and visits for tracking search behavior and personalization.
Typesense Analytics Operations API
Operational endpoints for managing the analytics subsystem.
Typesense Analytics Rules API
Create and manage analytics rules that control how search queries and user events are aggregated for query suggestions and relevance tuning.
Typesense Cluster Management API
Create, retrieve, update, and terminate Typesense Cloud clusters. Manage cluster lifecycle and generate Typesense Server API keys.
Typesense Configuration Changes API
Schedule, retrieve, list, and cancel configuration changes to running clusters such as memory upgrades, version changes, and HA toggles.
Typesense Server Configuration Parameters API
Manage Typesense Server configuration parameters for cloud clusters.
Open Collections 28
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).
API Collection
OPEN COLLECTIONTypesense Analytics API
OPEN COLLECTIONTypesense Analytics Analytics Events API
OPEN COLLECTIONTypesense Analytics Analytics Events Analytics Rules API
OPEN COLLECTIONTypesense Analytics Analytics Events API Keys API
OPEN COLLECTIONTypesense Cloud Management API
OPEN COLLECTIONTypesense Analytics Analytics Events Cluster Management API
OPEN COLLECTIONTypesense Analytics Analytics Events Collection Aliases API
OPEN COLLECTIONTypesense Analytics Analytics Events Collections API
OPEN COLLECTIONTypesense Analytics Analytics Events Configuration API
OPEN COLLECTIONTypesense Analytics Analytics Events Conversation Models API
OPEN COLLECTIONTypesense Analytics Analytics Events Curation Sets API
OPEN COLLECTIONTypesense Analytics Analytics Events Documents API
OPEN COLLECTIONTypesense Analytics Analytics Events Monitoring API
OPEN COLLECTIONTypesense Analytics Analytics Events Multi-Search API
OPEN COLLECTIONTypesense Analytics Analytics Events NL Search Models API
OPEN COLLECTIONTypesense Analytics Analytics Events Operations API
OPEN COLLECTIONTypesense Analytics Analytics Events Presets API
OPEN COLLECTIONTypesense Analytics Analytics Events Search API
OPEN COLLECTIONTypesense Analytics Analytics Events Stemming API
OPEN COLLECTIONTypesense Analytics Analytics Events Stopwords API
OPEN COLLECTIONTypesense Analytics Analytics Events Synonym Sets API
OPEN COLLECTIONTypesense Analytics Analytics Events Vector Collections API
OPEN COLLECTIONTypesense Analytics Analytics Events Vector Search API
OPEN COLLECTIONScroll within the panel for all 28 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Typesense GraphQL Schema
This GraphQL schema provides a conceptual type system for the [Typesense](https://typesense.org) open-source search engine REST API. Typesense is a fast, typo-tolerant search en...
GRAPHQLPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate 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.
Typesense 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.
Typesense Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Semantic Vocabularies 1
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.
Typesense 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.
Typesense API Rules
SPECTRALJSON Schema 66
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.
Typesense Analytics Event
JSON SCHEMAAnalyticsEvent
JSON SCHEMAAnalyticsEventCreateResponse
JSON SCHEMAAnalyticsEventCreateSchema
JSON SCHEMAAnalyticsRule
JSON SCHEMAAnalyticsRuleCreateSchema
JSON SCHEMAAnalyticsStatus
JSON SCHEMAApiKey
JSON SCHEMAApiKeySchema
JSON SCHEMAApiKeysResponse
JSON SCHEMACluster
JSON SCHEMAClusterApiKeys
JSON SCHEMAClusterCreateSchema
JSON SCHEMAClusterUpdateSchema
JSON SCHEMATypesense Collection
JSON SCHEMACollectionAlias
JSON SCHEMACollectionAliasesResponse
JSON SCHEMACollectionAliasSchema
JSON SCHEMACollectionResponse
JSON SCHEMACollectionSchema
JSON SCHEMACollectionUpdateSchema
JSON SCHEMAConfigurationChange
JSON SCHEMAConfigurationChangeCreateSchema
JSON SCHEMAConversationalSearchResult
JSON SCHEMAConversationModel
JSON SCHEMAConversationModelCreateSchema
JSON SCHEMAConversationModelUpdateSchema
JSON SCHEMACurationItem
JSON SCHEMACurationItemSchema
JSON SCHEMACurationSet
JSON SCHEMACurationSetSchema
JSON SCHEMADirtyValues
JSON SCHEMAEmbedConfig
JSON SCHEMAFacetCounts
JSON SCHEMAField
JSON SCHEMAHealthStatus
JSON SCHEMAIndexAction
JSON SCHEMAMultiSearchParameters
JSON SCHEMAMultiSearchResult
JSON SCHEMANLSearchModel
JSON SCHEMANLSearchModelCreateSchema
JSON SCHEMANLSearchModelUpdateSchema
JSON SCHEMAPreset
JSON SCHEMAPresetUpsertSchema
JSON SCHEMASchemaChangeStatus
JSON SCHEMATypesense Search Result
JSON SCHEMASearchGroupedHit
JSON SCHEMASearchHighlight
JSON SCHEMASearchResult
JSON SCHEMASearchResultHit
JSON SCHEMAServerConfigurationParameters
JSON SCHEMAStemmingDictionary
JSON SCHEMAStopwordsSet
JSON SCHEMAStopwordsSetUpsertSchema
JSON SCHEMASuccessStatus
JSON SCHEMASynonymItem
JSON SCHEMASynonymItemSchema
JSON SCHEMASynonymSet
JSON SCHEMASynonymSetSchema
JSON SCHEMAVectorCollectionResponse
JSON SCHEMAVectorCollectionSchema
JSON SCHEMAVectorField
JSON SCHEMAVectorMultiSearchParameters
JSON SCHEMAVectorSearchHit
JSON SCHEMAVectorSearchResult
JSON SCHEMAVoiceQueryModelConfig
JSON SCHEMAScroll within the panel for all 66 ·
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Typesense Collection Structure
JSON STRUCTURETypesense Search Result Structure
JSON STRUCTURETypesense Structure
JSON STRUCTUREExamples 4
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.
Typesense Search Example
EXAMPLESecurity 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 Typesense — 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 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
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/typesense · machine-readable index on apis.io
This is an independent, third-party profile of Typesense, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.