Nex
Nex is the workflow execution and context layer for AI-native business operations — where AI workflows become reliable business software. It builds a unified context graph from a company's connected tools (email, calendar, Slack, and CRMs like HubSpot, Salesforce, and Attio) plus ingested unstructured context, then grounds AI agents in that shared organizational memory. The Nex Developer API is a REST API over the context graph: define object types and attributes, create records and typed relationships, group them into lists, attach tasks and notes, read record timelines, ingest context, ask grounded natural-language questions, stream AI-derived insights over SSE, run full-text search, and trigger compounding intelligence jobs. Authentication is via scoped API keys, and organizational context is also exposed to agents through a first-party Model Context Protocol (MCP) server shipped as the nex CLI.
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 Nex the way a machine reads it — 21 machine-readable artifacts across 16 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 — Nex scores 48.8/100 (developing), with a separate agent-readiness read of 65/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 Nex
Each block below is one kind of artifact we hold for Nex. 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 16
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.
Nex AI Lists API
The AI Lists API from Nex — 2 operation(s) for ai lists.
Nex Compounding API
The Compounding API from Nex — 2 operation(s) for compounding.
Nex Context API
The Context API from Nex — 3 operation(s) for context.
Nex Graph API
The Graph API from Nex — 1 operation(s) for graph.
Nex Insights API
The Insights API from Nex — 2 operation(s) for insights.
Nex Integrations API
The Integrations API from Nex — 4 operation(s) for integrations.
Nex Lists API
The Lists API from Nex — 4 operation(s) for lists.
Nex Notes API
The Notes API from Nex — 2 operation(s) for notes.
Nex Notifications API
The Notifications API from Nex — 4 operation(s) for notifications.
Nex Objects API
The Objects API from Nex — 1 operation(s) for objects.
Nex Records API
The Records API from Nex — 3 operation(s) for records.
Nex Relationships API
The Relationships API from Nex — 4 operation(s) for relationships.
Nex Schema API
The Schema API from Nex — 4 operation(s) for schema.
Nex Search API
The Search API from Nex — 1 operation(s) for search.
Nex Tasks API
The Tasks API from Nex — 2 operation(s) for tasks.
Nex Timeline API
The Timeline API from Nex — 1 operation(s) for timeline.
Scroll within the panel for all 16 ·
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.
nex-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 Nex — 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 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/nex · machine-readable index on apis.io