Developers

One developer contract: a REST API, an MCP server with 39 agent-callable tools, and a fully-typed TypeScript SDK — all speaking one record schema from one canonical domain.

Quickstart

# 1. Create a scoped API key from the dashboard (Pro/Team)
#    Dashboard → API Keys → + Create key

# 2. Create your first record
curl -X POST https://api.nexusrelate.com/v1/records \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer nxs_live_..." \
  -d '{
    "object": "contact",
    "attributes": { "name": "Acme Corp", "stage": "prospect" }
  }'

⚡

API Reference

Every /v1 endpoint: auth, records, posts, campaigns, transduction, agent, testing, billing, audit.

🤖

MCP Server

39 agent-callable tools behind scoped tokens and approval gates.

◈

TypeScript SDK

Fully-typed @nexus/sdk client for server-side and edge runtimes.

📄

OpenAPI Spec

Machine-readable artifacts generated from the registries — openapi.json, mcp-tools.json, entitlements.json, llms.txt.

What you can rely on

One base URL

All production calls go to https://api.nexusrelate.com. No raw infrastructure URLs.

One record schema

REST, SDK, and MCP all use object/object_slug + attributes. Examples are generated from the same registries that serve production.

Versioning

All endpoints are versioned under /v1. Breaking changes receive a deprecation window and a migration guide.

Agent safety

Agent actions are scoped by token permissions and risk class. Reads run automatically within scope. Writes are scope-checked and logged. Financial actions (spending money, equity grants, billing) and bulk outreach always require human approval before executing.

← Back to home