NextNeural AI Binaries
This is the API reference for the four Go service binaries in the nextneural_ai
workspace. Each one deploys independently, keeps its own Postgres database, and
serves its own HTTP API.
| Binary | What it does | Default port |
|---|---|---|
| nextneural_converse → | Autonomous voice agent — inbound and outbound AI phone calls | 8080 |
| nextneural_intel → | Post-call batch analysis of uploaded recordings | 8080 |
| nextneural_assist → | Real-time in-call coaching for human agents | 8080 |
| nextneural_coach → | Simulated-call training and scoring | 8010 |
These pages use the product names above. On disk the Go modules, make targets
and databases use the short form — nn_converse, nn_intel, nn_assist,
nn_coach — so every command in this documentation uses those. They refer to
the same four services.
All four run on port 8080 by default except nextneural_coach, so a machine running
more than one needs PORT set per service. See Running a binary.
Where to start
| Quickstart → | Sign up, create an API key, make your first call |
| Architecture → | How the four binaries relate, and what they share |
| Authentication → | Sessions, API keys, scopes, and roles |
Two API surfaces
Every binary serves two kinds of endpoint, and the difference decides how you authenticate:
Console API — what the bundled web UI calls. Authenticated with a session
JWT from POST /api/auth/login. This is the larger surface: it covers
configuration, team management, and everything an operator does in the browser.
Developer API — for server-to-server integration, authenticated with an API
key (nn_k_…). Deliberately narrower, and scoped: a key grants only the
permissions you select when you create it. nextneural_converse exposes this at /v1,
nextneural_intel at /api/v1/sales.
nextneural_coach is the exception: it accepts either credential on the same routes,
with role-gated routes refusing keys outright.
Both surfaces scope every query to the caller's organization. That boundary is identical regardless of which credential you use.
What these binaries share
All four are built on the same platform/ Go module, so the following behaves
identically across them and is documented once under Common:
- Signup with email OTP verification, login, and password reset
- Organization setup, membership, and roles (
admin,manager,member) - Waitlist approval gating for new organizations
- API key issuance, scoping, and revocation
- The error response shape
Self-hosted
These binaries are deployed to your own infrastructure — there is no shared
hosted endpoint. Every example here uses https://your-host as a placeholder.
Substitute whatever hostname and port your deployment serves on.