lakeFS
Manage your data as code using Git-like operations and achieve reproducible, high-quality data pipelines. Start locally, run on-prem or in the cloud.
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 lakeFS the way a machine reads it — 24 machine-readable artifacts across 17 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 — lakeFS scores 35.6/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 lakeFS
Each block below is one kind of artifact we hold for lakeFS. 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 17
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.
lakeFS actions API
The actions API from lakeFS — 4 operation(s) for actions.
lakeFS auth API
The auth API from lakeFS — 23 operation(s) for auth.
lakeFS branches API
The branches API from lakeFS — 5 operation(s) for branches.
lakeFS commits API
The commits API from lakeFS — 2 operation(s) for commits.
lakeFS config API
The config API from lakeFS — 1 operation(s) for config.
lakeFS experimental API
The experimental API from lakeFS — 14 operation(s) for experimental.
lakeFS external API
The external API from lakeFS — 4 operation(s) for external.
lakeFS healthCheck API
The healthCheck API from lakeFS — 1 operation(s) for healthcheck.
lakeFS import API
The import API from lakeFS — 1 operation(s) for import.
lakeFS internal API
The internal API from lakeFS — 24 operation(s) for internal.
lakeFS metadata API
The metadata API from lakeFS — 2 operation(s) for metadata.
lakeFS objects API
The objects API from lakeFS — 8 operation(s) for objects.
lakeFS pulls API
The pulls API from lakeFS — 3 operation(s) for pulls.
lakeFS refs API
The refs API from lakeFS — 3 operation(s) for refs.
lakeFS repositories API
The repositories API from lakeFS — 7 operation(s) for repositories.
lakeFS staging API
The staging API from lakeFS — 1 operation(s) for staging.
lakeFS tags API
The tags API from lakeFS — 2 operation(s) for tags.
Scroll within the panel for all 17 ·
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).
lakeFS 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.
Lakefs 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.
Lakefs 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.
Lakefs 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 lakeFS — 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
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lakefs · machine-readable index on apis.io