Compresr
Compresr is an LLM context-compression API. You send the long context you would otherwise pass to a model plus the query you want answered, and Compresr returns a shorter context that keeps the answer-bearing spans and drops the rest — fewer input tokens, lower cost, a longer effective context window, and faster inference. It sits in front of whatever LLM stack you already use and replaces nothing. The public API exposes query-specific compression models (latte_v1 and the faster latte_v2) plus tool-output, conversation-history, and tool-discovery variants, over a hosted HTTP API with Python and TypeScript SDKs, first-party framework integrations (LangChain, LangGraph, LlamaIndex, LiteLLM), and per-key tiered rate limits. Compresr Inc. is a Y Combinator W26 company built by four EPFL-trained researchers in San Francisco, California and Switzerland.
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 Compresr the way a machine reads it — 34 machine-readable artifacts across 27 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 — Compresr scores 58.5/100 (developing), with a separate agent-readiness read of 81/100 (agent native). 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 Compresr
Each block below is one kind of artifact we hold for Compresr. 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 27
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.
Compresr Admin API
The Admin API from Compresr — 18 operation(s) for admin.
Compresr Admin - Whitelist API
The Admin - Whitelist API from Compresr — 4 operation(s) for admin - whitelist.
Compresr API Keys API
The API Keys API from Compresr — 4 operation(s) for api keys.
Compresr Auth API
The Auth API from Compresr — 1 operation(s) for auth.
Compresr Billing API
The Billing API from Compresr — 10 operation(s) for billing.
Compresr Careers API
The Careers API from Compresr — 12 operation(s) for careers.
Compresr Compresr Platform API API
The Compresr Platform API API from Compresr — 1 operation(s) for compresr platform api.
Compresr Compression-Agentic API
The Compression-Agentic API from Compresr — 18 operation(s) for compression-agentic.
Compresr Compression API
The Compression API from Compresr — 6 operation(s) for compression.
Compresr Compression-Demo API
The Compression-Demo API from Compresr — 5 operation(s) for compression-demo.
Compresr Compression-Models API
The Compression-Models API from Compresr — 2 operation(s) for compression-models.
Compresr Dashboard API
The Dashboard API from Compresr — 1 operation(s) for dashboard.
Compresr Feature Requests API
The Feature Requests API from Compresr — 3 operation(s) for feature requests.
Compresr Gateway API
The Gateway API from Compresr — 5 operation(s) for gateway.
Compresr Health API
The Health API from Compresr — 3 operation(s) for health.
Compresr Inference API
The Inference API from Compresr — 1 operation(s) for inference.
Compresr Logs API
The Logs API from Compresr — 1 operation(s) for logs.
Compresr Metrics API
The Metrics API from Compresr — 2 operation(s) for metrics.
Compresr Newsletter API
The Newsletter API from Compresr — 4 operation(s) for newsletter.
Compresr OAuth API
The OAuth API from Compresr — 6 operation(s) for oauth.
Compresr OAuth Authorization API
The OAuth Authorization API from Compresr — 3 operation(s) for oauth authorization.
Compresr On-Prem API
The On-Prem API from Compresr — 1 operation(s) for on-prem.
Compresr On-Prem Telemetry API
The On-Prem Telemetry API from Compresr — 3 operation(s) for on-prem telemetry.
Compresr Pricing API
The Pricing API from Compresr — 2 operation(s) for pricing.
Compresr Profile API
The Profile API from Compresr — 6 operation(s) for profile.
Compresr Ready API
The Ready API from Compresr — 1 operation(s) for ready.
Compresr Usage API
The Usage API from Compresr — 1 operation(s) for usage.
Scroll within the panel for all 27 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
compresr-mcp.yml
MCP SERVERPricing 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.
Compresr Plans
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.
Compresr 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.
Compresr 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 Compresr — 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 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/compresr · machine-readable index on apis.io