N3XT
N3XT is a Wyoming state-chartered Special Purpose Depository Institution (SPDI) offering instant, 24/7/365 USD payment settlement for business-to-business transactions on blockchain rails. Its full-reserve narrow-bank model backs every deposit 1:1 with cash and short-term U.S. Treasuries (no lending), and it issues the N3XT Digital Dollar (NDD) — a bank-regulated tokenized deposit with an on-chain KYC/KYB Identity Passport (NDDID). The N3XT API is a holistic banking API for businesses covering wallets and public-wallet onboarding, instant and programmable payments, payment requests, internal transfers, NDD mint/redeem, contacts, approvals and audit trail. It ships OAuth 2.0 authentication, Beta/Omega test environments, and a first-party hosted MCP server for AI/agent access.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles N3XT 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 — N3XT scores 60.0/100 (strong), with a separate agent-readiness read of 58/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 N3XT
Each block below is one kind of artifact we hold for N3XT. 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.
N3XT Approvals API
The Approvals API from N3XT — 2 operation(s) for approvals.
N3XT AuditTrail API
The AuditTrail API from N3XT — 1 operation(s) for audittrail.
N3XT Businesses API
The Businesses API from N3XT — 2 operation(s) for businesses.
N3XT Contacts API
The Contacts API from N3XT — 2 operation(s) for contacts.
N3XT Ndd Routes API
The Ndd Routes API from N3XT — 2 operation(s) for ndd routes.
N3XT Payments API
The Payments API from N3XT — 5 operation(s) for payments.
N3XT Programmable API
The Programmable API from N3XT — 5 operation(s) for programmable.
N3XT System API
The System API from N3XT — 2 operation(s) for system.
N3XT Transfers API
The Transfers API from N3XT — 1 operation(s) for transfers.
N3XT Users API
The Users API from N3XT — 2 operation(s) for users.
N3XT Wallets API
The Wallets API from N3XT — 6 operation(s) for wallets.
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.
n3xt-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.
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 N3XT — 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 5
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
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 2
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/n3xt · machine-readable index on apis.io