Adapter
Adapter is a cognition API — a persistent memory and knowledge-graph layer that sits alongside AI models so understanding is already available when agents need answers. Founded by Adam Ghetti and David Bader, Adapter continuously reads and connects a user's data (calendar, contacts, messages, email, conversations) into a living knowledge graph, grounding every response in cited sources and surfacing hidden connections across sources rather than starting each query from scratch. The Adapter API exposes multi-model conversation/completion endpoints, knowledge-graph and memory queries, life-radar events, reminders, multi-channel messaging, reranking, and an OAuth 2.0 + hosted MCP surface (mcp:read) for agent access. Tagline: "Give your model a mind."
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 Adapter the way a machine reads it — 31 machine-readable artifacts across 26 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 — Adapter scores 35.5/100 (thin), with a separate agent-readiness read of 69/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Adapter
Each block below is one kind of artifact we hold for Adapter. 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 26
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.
Adapter Adapter API API
The Adapter API API from Adapter — 1 operation(s) for adapter api.
Adapter assets API
The assets API from Adapter — 8 operation(s) for assets.
Adapter auth API
The auth API from Adapter — 23 operation(s) for auth.
Adapter conversations API
The conversations API from Adapter — 11 operation(s) for conversations.
Adapter Docs API
The Docs API from Adapter — 1 operation(s) for docs.
Adapter Imessage API
The Imessage API from Adapter — 1 operation(s) for imessage.
Adapter knowledge API
The knowledge API from Adapter — 11 operation(s) for knowledge.
Adapter life API
The life API from Adapter — 1 operation(s) for life.
Adapter Line API
The Line API from Adapter — 1 operation(s) for line.
Adapter location API
The location API from Adapter — 1 operation(s) for location.
Adapter management API
The management API from Adapter — 1 operation(s) for management.
Adapter Oauth API
The Oauth API from Adapter — 1 operation(s) for oauth.
Adapter oauth-connect API
The oauth-connect API from Adapter — 3 operation(s) for oauth-connect.
Adapter oauth2 API
The oauth2 API from Adapter — 2 operation(s) for oauth2.
Adapter Openapi.json API
The Openapi.json API from Adapter — 1 operation(s) for openapi.json.
Adapter proxy API
The proxy API from Adapter — 13 operation(s) for proxy.
Adapter radar API
The radar API from Adapter — 2 operation(s) for radar.
Adapter Redoc API
The Redoc API from Adapter — 1 operation(s) for redoc.
Adapter reminders API
The reminders API from Adapter — 3 operation(s) for reminders.
Adapter reranking API
The reranking API from Adapter — 1 operation(s) for reranking.
Adapter Sendblue API
The Sendblue API from Adapter — 1 operation(s) for sendblue.
Adapter Sms API
The Sms API from Adapter — 1 operation(s) for sms.
Adapter support API
The support API from Adapter — 1 operation(s) for support.
Adapter Users API
The Users API from Adapter — 1 operation(s) for users.
Adapter Webhook API
The Webhook API from Adapter — 3 operation(s) for webhook.
Adapter Whatsapp API
The Whatsapp API from Adapter — 2 operation(s) for whatsapp.
Scroll within the panel for all 26 ·
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.
adapter-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.
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 Adapter — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/adapter · machine-readable index on apis.io