WHAT IS RGX

RGX Systems is a wholesale software integration substrate for Value-Added Resellers. You are not reselling RGX — you are building your own product on top of it. Your clients never know RGX exists.

The platform gives you a single authenticated API surface that connects to every tool your clients use — CRM, email, calendar, messaging channels, file storage, and calling — and exposes them through a consistent set of REST endpoints scoped to your VAR node.

How Your Node Works

Every VAR operator receives a VAR node — an isolated multi-tenant container that holds all your client records, credentials, usage events, and billing data. Nothing from your node is visible to other operators. Nothing from other operators is visible to yours.

Architecture at a Glance

GETTING STARTED

Once you have your Master API Key, you can have your first client registered and connected within minutes. All endpoints are under https://rgxsystems.com/api/v1/.

Step 1 — Verify Your Node

Confirm your key is active and your node is live before building anything.

GET /api/v1/health
X-Api-Key: rgx_live_your_key_here

// Response
{
  "ok": true,
  "node": "Acme MSP",
  "plan": "standard",
  "timestamp": "2026-05-22T09:00:00Z"
}

Step 2 — Register a Client

Every client gets a client_ref — a unique identifier you define. Use whatever makes sense in your system (account ID, slug, etc.).

POST /api/v1/clients
X-Api-Key: rgx_live_your_key_here

{
  "client_ref": "contoso-ltd",
  "name": "Contoso Ltd",
  "email": "ops@contoso.com"
}

// Response
{ "ok": true, "client_ref": "contoso-ltd", "id": "cli_…" }

Step 3 — Connect an Integration

Credentials are encrypted with AES-256-GCM immediately on write and never returned in plaintext. Only one integration per type per client.

POST /api/v1/clients/contoso-ltd/connect
X-Api-Key: rgx_live_your_key_here

{
  "type": "hubspot",
  "config": { "api_key": "their_hubspot_key" }
}

Step 4 — Use the Data

GET /api/v1/clients/contoso-ltd/crm/deals
X-Api-Key: rgx_live_your_key_here

// Response
{
  "ok": true,
  "deals": [ { "id": "deal_001", "name": "Q2 Renewal", "stage": "Proposal", "value": 24000 } ],
  "count": 1
}

MANAGING CLIENTS

Clients are the core tenant unit under your VAR node. Each client has isolated credential storage, configuration, channel history, and call logs. A client maps to one of your end customers.

Client CRUD Endpoints

Cursor Pagination

The GET /clients endpoint and all list endpoints return a next_cursor token when more records exist. Pass it back as ?cursor=… on the next request. No offset arithmetic, no missed records.

GET /api/v1/clients?limit=25
// Response
{ "clients": [...], "next_cursor": "eyIyMDI2..." }

GET /api/v1/clients?limit=25&cursor=eyIyMDI2...
// Next page

Connecting Integrations

Each client can have one integration per type. Credentials are encrypted on write and decrypted in-memory only at runtime.

CHANNELS & CALL LOGS

Ingest Pipeline

The /ingest endpoint is your primary payload logging endpoint. Use it to record any communication event into your node. All ingested messages are stored, validated, and queryable.

POST /api/v1/ingest
{
  "client_ref": "contoso-ltd",
  "messages": [
    { "role": "user", "content": "When does my contract renew?" },
    { "role": "assistant", "content": "Your contract renews August 1st." }
  ],
  "channel": "sms",
  "process_with_ai": false  // set true to auto-generate summary
}

Channel-Specific Ingest

For richer per-client storage with channel metadata, use the client-scoped channel ingest endpoint:

POST /api/v1/clients/contoso-ltd/channels/ingest
{
  "channel": "email",
  "direction": "inbound",
  "from_address": "client@contoso.com",
  "subject": "Renewal question",
  "body_preview": "Hi, when does my contract renew?",
  "external_id": "msg_abc123"
}

Bulk Ingest

Up to 100 messages across multiple clients in a single call. Per-item success/failure results returned. Usage tracked in aggregate.

POST /api/v1/bulk/ingest
{
  "items": [
    { "client_ref": "contoso-ltd", "messages": [...], "channel": "slack" },
    { "client_ref": "fabrikam-inc", "messages": [...], "channel": "whatsapp" }
  ]
}

Call Logging

Log calls with full transcripts. Summaries and action items auto-extracted and stored per record.

POST /api/v1/clients/contoso-ltd/calls/log
{
  "direction": "inbound",
  "from_number": "+14155551234",
  "duration_seconds": 312,
  "transcript": "Full transcript text here..."
}

Querying History

EMAIL, CALENDAR & FILES

Email

Full inbox access and send capability. Works across Gmail, Outlook/M365, and any IMAP provider. Requires a gmail, outlook, or imap integration to be connected for the client.

Calendar

Google Calendar and Outlook Calendar. Accessible via the gmail or outlook integration — no separate connection required.

Messaging — Slack & SMS

Files

List and search files from Google Drive or OneDrive. Accessible via the gmail (Drive) or outlook (OneDrive) integration.

GET /api/v1/clients/contoso-ltd/files?q=contract+2026

// Response
{
  "files": [
    { "id": "1BxiM…", "name": "Contoso_Contract_2026.pdf", "webViewLink": "https://…" }
  ]
}

PROCESSING & KNOWLEDGE

The /process Endpoint

Send any text input and receive a structured response from the processing pipeline. Optionally scope it to a client to apply their stored configuration automatically.

POST /api/v1/process
{
  "input": "Summarize the last 3 deals in our pipeline",
  "client_ref": "contoso-ltd",  // applies stored system prompt
  "session_id": "sess_abc"
}

// Response
{ "response": "...", "processing_ms": 740, "units_used": 388 }

Per-Client Processing Config

Store a system prompt and output length configuration per client. Applied automatically on every /process and /ingest call scoped to that client.

PATCH /api/v1/clients/contoso-ltd/ai-config
{
  "system_prompt": "You are a business assistant for Contoso Ltd. Always respond concisely and focus on their IT infrastructure priorities.",
  "max_tokens": 1024
}

Knowledge Base

Store reference material, SOPs, policies, and documents per client. Searched and injected as context on processing requests. Fully queryable and updatable.

POST /api/v1/clients/contoso-ltd/knowledge
{
  "title": "Contoso SLA Policy",
  "content": "P1 incidents must be acknowledged within 15 minutes...",
  "tags": ["sla", "policy"]
}

WEBHOOKS & SUB-KEYS

Webhooks

Register an HTTPS endpoint on your VAR node to receive push events in real-time. Payloads are HMAC-SHA256 signed — verify the X-RGX-Signature header on every delivery.

POST /api/v1/webhooks
{
  "url": "https://yourapp.com/webhooks/rgx",
  "events": ["message.ingested", "call.logged", "client.created"],
  "label": "Production Receiver"
}

// Response — signing secret shown ONCE, store it immediately
{ "id": "wh_…", "signing_secret": "whsec_…" }

const sig = req.headers['x-rgx-signature'];
const expected = crypto
  .createHmac('sha256', 'whsec_your_secret')
  .update(JSON.stringify(req.body))
  .digest('hex');
if (sig !== expected) return res.status(401).end();

Sub-Keys — Scoped Access for Your Clients

Issue API keys directly to your clients so they can call the platform themselves — without exposing your master key. Sub-keys authenticate against your VAR node and are revocable at any time.

POST /api/v1/clients/contoso-ltd/keys
{ "label": "Contoso Portal Key" }

// Response — raw key shown once
{ "key": "rgx_live_sub_…", "id": "ck_…" }

USAGE & BILLING

Pricing Model

Two components — a flat monthly base fee plus a per-seat charge for each active client on your node.

Usage Endpoints

GET /api/v1/usage

// Response
{
  "current_month": {
    "requests": 4821,
    "messages": 18340,
    "active_seats": 20,
    "seat_charges_usd": 1200.00,
    "estimated_invoice_usd": 3200.00
  },
  "history": [...]
}

Aggregate Reporting

Get a full breakdown of activity across your entire book of clients in a single call.

Security Summary

FULL ENDPOINT REFERENCE

Core

Clients

CRM · Email · Calendar · Files

Channels · Calls · Slack · SMS · Processing · Knowledge · Webhooks · Reporting