Flatfile
Flatfile is a data exchange platform that helps teams import, transform, validate, and collaborate on file-based data. The Flatfile API provides programmatic access to spaces, workbooks, sheets, records, files, documents, jobs, events, agents, environments, users, guests, and related primitives for building automated data onboarding and ingestion workflows.
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 Flatfile the way a machine reads it — 41 machine-readable artifacts across 32 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 — Flatfile scores 49.9/100 (developing), with a separate agent-readiness read of 60/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 Flatfile
Each block below is one kind of artifact we hold for Flatfile. 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 32
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.
Flatfile subpackage_accounts API
The subpackage_accounts API from Flatfile — 1 operation(s) for subpackage_accounts.
Flatfile subpackage_actions API
The subpackage_actions API from Flatfile — 3 operation(s) for subpackage_actions.
Flatfile subpackage_agent-exports API
The subpackage_agent-exports API from Flatfile — 3 operation(s) for subpackage_agent-exports.
Flatfile subpackage_agents API
The subpackage_agents API from Flatfile — 10 operation(s) for subpackage_agents.
Flatfile subpackage_apps API
The subpackage_apps API from Flatfile — 6 operation(s) for subpackage_apps.
Flatfile subpackage_assistant API
The subpackage_assistant API from Flatfile — 2 operation(s) for subpackage_assistant.
Flatfile subpackage_auth API
The subpackage_auth API from Flatfile — 2 operation(s) for subpackage_auth.
Flatfile subpackage_canvas-areas API
The subpackage_canvas-areas API from Flatfile — 2 operation(s) for subpackage_canvas-areas.
Flatfile subpackage_commits API
The subpackage_commits API from Flatfile — 3 operation(s) for subpackage_commits.
Flatfile subpackage_data-clips API
The subpackage_data-clips API from Flatfile — 6 operation(s) for subpackage_data-clips.
Flatfile subpackage_data-retention-policies API
The subpackage_data-retention-policies API from Flatfile — 2 operation(s) for subpackage_data-retention-policies.
Flatfile subpackage_documents API
The subpackage_documents API from Flatfile — 2 operation(s) for subpackage_documents.
Flatfile subpackage_entitlements API
The subpackage_entitlements API from Flatfile — 1 operation(s) for subpackage_entitlements.
Flatfile subpackage_environments API
The subpackage_environments API from Flatfile — 6 operation(s) for subpackage_environments.
Flatfile subpackage_events API
The subpackage_events API from Flatfile — 4 operation(s) for subpackage_events.
Flatfile subpackage_files API
The subpackage_files API from Flatfile — 5 operation(s) for subpackage_files.
Flatfile subpackage_flags API
The subpackage_flags API from Flatfile — 3 operation(s) for subpackage_flags.
Flatfile subpackage_guests API
The subpackage_guests API from Flatfile — 6 operation(s) for subpackage_guests.
Flatfile subpackage_jobs API
The subpackage_jobs API from Flatfile — 12 operation(s) for subpackage_jobs.
Flatfile subpackage_mapping API
The subpackage_mapping API from Flatfile — 4 operation(s) for subpackage_mapping.
Flatfile subpackage_records API
The subpackage_records API from Flatfile — 4 operation(s) for subpackage_records.
Flatfile subpackage_roles API
The subpackage_roles API from Flatfile — 1 operation(s) for subpackage_roles.
Flatfile subpackage_routines API
The subpackage_routines API from Flatfile — 2 operation(s) for subpackage_routines.
Flatfile subpackage_runbooks API
The subpackage_runbooks API from Flatfile — 2 operation(s) for subpackage_runbooks.
Flatfile subpackage_secrets API
The subpackage_secrets API from Flatfile — 2 operation(s) for subpackage_secrets.
Flatfile subpackage_sheets API
The subpackage_sheets API from Flatfile — 11 operation(s) for subpackage_sheets.
Flatfile subpackage_snapshots API
The subpackage_snapshots API from Flatfile — 4 operation(s) for subpackage_snapshots.
Flatfile subpackage_spaces API
The subpackage_spaces API from Flatfile — 8 operation(s) for subpackage_spaces.
Flatfile subpackage_users API
The subpackage_users API from Flatfile — 6 operation(s) for subpackage_users.
Flatfile subpackage_versions API
The subpackage_versions API from Flatfile — 1 operation(s) for subpackage_versions.
Flatfile subpackage_views API
The subpackage_views API from Flatfile — 2 operation(s) for subpackage_views.
Flatfile subpackage_workbooks API
The subpackage_workbooks API from Flatfile — 3 operation(s) for subpackage_workbooks.
Scroll within the panel for all 32 ·
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).
API Reference
OPEN COLLECTIONMCP 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.
MCP Server
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.
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.
Flatfile 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.
Flatfile Finops
FINOPSSecurity Posture 3
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 Flatfile — 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 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
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
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/flatfile · machine-readable index on apis.io