Trieve
Trieve (Devflow, Inc.) is an open-source, all-in-one search, recommendations, RAG, and analytics platform delivered as a REST API. The backend is written in Rust (Actix-web) and exposes endpoints for managing organizations, datasets, chunks, chunk groups, files, search, topics / messages (LLM chat), web crawls, events, analytics, and experiments. Trieve Cloud is hosted at api.trieve.ai; the same server can be self-hosted from the devflowinc/trieve repository. Official SDKs are published for TypeScript and Python.
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 Trieve the way a machine reads it — 28 machine-readable artifacts across 21 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 — Trieve scores 38.5/100 (thin), 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 Trieve
Each block below is one kind of artifact we hold for Trieve. 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 21
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.
Trieve REST API
Production REST API for Trieve Cloud. Organizes resources around organizations, datasets, chunks, chunk groups, files, search, topics, messages, crawls, analytics, events, exper...
Trieve Chunk API
Manage chunks - the individual searchable units of content stored in a dataset - including create, update, delete, get, and bulk operations.
Trieve Chunk Group API
Group chunks into bookmark-style folders for organization, recommendations, and group-scoped search within a dataset.
Trieve Dataset API
Create and configure datasets that hold chunks, chunk groups, and search / RAG configuration for a workload.
Trieve Search API
Run vector, full-text, and hybrid search across a dataset, with filters, boosts, re-ranking, and highlights.
Trieve File API
Upload files (up to 1 GB), extract text, and chunk them into a dataset. Asynchronous - completion is signaled via the Events API.
Trieve Topic API
Topics persist conversational state for generative-AI chat sessions backed by a Trieve dataset.
Trieve Message API
Messages are turns within a topic; the Message API drives RAG completions, streaming responses, and citation-aware chat against a dataset.
Trieve Crawl API
Create and manage web crawls that ingest pages into a dataset for search and RAG.
Trieve Analytics API
Query search and RAG analytics - top queries, no-result queries, latency, click-through, and experiment outcomes.
Trieve Events API
Server-sent notifications about asynchronous work such as file processing, crawl completion, and chunk ingestion.
Trieve Organization API
Manage organizations, roles, and members.
Trieve Auth API
Registration, login, and session handling for Trieve users.
Trieve TypeScript SDK
Official TypeScript / JavaScript client library for the Trieve REST API.
Trieve Python SDK
Official Python client library (trieve-py-client) for the Trieve REST API.
Trieve Open Source Server
Self-hostable Trieve server (Rust / Actix-web), dashboard, search and chat UIs, ingestion / file / delete workers, batch-ETL utilities, pdf2md converter, and Helm charts for Kub...
Trieve Chunk API
The Chunk API from Trieve — 1 operation(s) for chunk.
Trieve Dataset API
The Dataset API from Trieve — 1 operation(s) for dataset.
Trieve File API
The File API from Trieve — 1 operation(s) for file.
Trieve Message API
The Message API from Trieve — 1 operation(s) for message.
Trieve Topic API
The Topic API from Trieve — 1 operation(s) for topic.
Scroll within the panel for all 21 ·
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).
Trieve 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.
Trieve 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.
Trieve 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.
Trieve Finops
FINOPSSecurity 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 Trieve — 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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
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/trieve · machine-readable index on apis.io