Hex
Hex is an AI-powered analytics platform that combines agentic notebooks, interactive data apps, and conversational self-serve analytics so teams can go from ad-hoc exploration to published, governed data apps. The Hex External API (bearer-token authenticated, base https://app.hex.tech/api/v1) lets you programmatically run and schedule projects, manage projects, collections, groups, cells, and data connections, ingest semantic models, drive AI agent Threads (create, continue, read messages), export projects, and administer workspace users. Hex also ships a first-party CLI, a hosted remote MCP server, Airflow and Dagster integrations, and published Claude Agent Skills. Surfaced as an a16z portfolio company and enriched with its real public developer surface.
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 Hex the way a machine reads it — 17 machine-readable artifacts across 11 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 — Hex scores 56.0/100 (developing), with a separate agent-readiness read of 72/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 Hex
Each block below is one kind of artifact we hold for Hex. 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 11
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.
Hex Cells API
The Cells API from Hex — 4 operation(s) for cells.
Hex Collections API
The Collections API from Hex — 2 operation(s) for collections.
Hex Context API
The Context API from Hex — 1 operation(s) for context.
Hex Data Connections API
The Data Connections API from Hex — 3 operation(s) for data connections.
Hex Embedding API
The Embedding API from Hex — 1 operation(s) for embedding.
Hex Groups API
The Groups API from Hex — 2 operation(s) for groups.
Hex Guides API
The Guides API from Hex — 4 operation(s) for guides.
Hex Projects API
The Projects API from Hex — 11 operation(s) for projects.
Hex Semantic (projects|models) API
The Semantic (projects|models) API from Hex — 2 operation(s) for semantic (projects|models).
Hex Threads API
The Threads API from Hex — 4 operation(s) for threads.
Hex Users API
The Users API from Hex — 3 operation(s) for users.
Scroll within the panel for all 11 ·
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.
hex-mcp.yml
MCP SERVERSecurity Posture 4
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.
Hex Trust Center
SOC 2 Type II, HIPAA, PCI, GDPR, CCPA, EU-US Data Privacy Framework, Swiss-US Data Privacy Framework, UK-US Data Privacy Framework
SECURITYAgentic 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 Hex — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hex · machine-readable index on apis.io