Fixture
Fixture is an AI-native CRM built for startups, backed by Y Combinator (Winter 2026 batch). Fixture aggregates every customer interaction — email, calendar, Slack and Slack Connect, meeting notes from Granola, Notion and Circleback, and Stripe billing events — into a single structured activity graph across Accounts, Contacts, Deals, Leads, Tasks and Notes, then uses agents to surface next actions and keep records current without manual data entry. The whole system is programmable — Fixture publishes a documented REST v1 API with a generated OpenAPI 3.1 description, a hosted remote MCP server with OAuth 2.1 and dynamic client registration, and a first-party agent-oriented CLI, so humans and agents work against the same 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 Fixture the way a machine reads it — 15 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 — Fixture scores 47.1/100 (developing), with a separate agent-readiness read of 70/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 Fixture
Each block below is one kind of artifact we hold for Fixture. 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.
Fixture Accounts API
Create, read, update, and delete company records.
Fixture Activities API
List and ingest CRM Activity records.
Fixture Contacts API
Create, read, update, and delete person records.
Fixture Deals API
Create, read, update, and delete Deal records.
Fixture Fixture API API
The Fixture API API from Fixture — 1 operation(s) for fixture api.
Fixture Leads API
Create, read, update, and convert Leads.
Fixture Notes API
Create Notes linked to CRM entities.
Fixture Pipelines API
List Pipelines and inspect their nested stages.
Fixture Task Statuses API
List Task status definitions available to the current organization.
Fixture Tasks API
Create, read, update, and delete Tasks.
Fixture Users API
The Users API from Fixture — 1 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.
fixture-mcp.yml
MCP SERVERSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Fixture — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fixture · machine-readable index on apis.io