Developer platform

Build on the lab.

Sales Lab is a training infrastructure layer, not just a sales roleplay app. REST moves scenarios and progress, signed webhooks move events, CRM connectors keep managers in their existing systems, and the MCP server lets your AI agents assign practice or read scorecards with scoped tenant access.

Read the API reference

The surface

Bring every training system into the lab.

Nothing here is a private back door. Each surface is documented, versioned, and scoped. The same primitives can train B2B reps, support teams, new hires, retail staff, restaurant servers, field sellers, or anyone who needs coached spoken practice.

REST API

api/v1

Sessions, scorecards, scenarios, real-call ingests, coaching briefs, and portable progress. Bearer-token auth with granular per-scope grants — a token can read scorecards without touching billing or people.

Reference

CRM handoff

Salesforce sync, HubSpot notes, and pipeline systems

Salesforce turns opportunity context into practice. HubSpot receives verified scorecard notes. Scoped APIs and webhooks carry progress into the rest of your operating system.

Reference

Outbound webhooks

Signed events, five retries

HMAC-SHA256 signatures, idempotent delivery IDs, exponential backoff. Core event kinds are wired today — scorecards, certifications, real-call ingests, assignments, tournaments, coverage, and tier changes fire the moment they land.

Reference

MCP server

For Claude, GPT, and Cursor

A stdio MCP server your AI agents can run locally or in your own container. Let existing copilots read progress, assign practice, generate scenarios, and move trainees through your learning loop.

Reference

Training graph

One progress layer for any role

Sales, customer support, onboarding, retail, hospitality, field teams, accent practice, and speech coaching all write to the same scenario → attempt → feedback → retry model.

Reference

Consent ledger

Hash-chained, and public

Every voice-clone consent event, appended to a public hash-chained ledger. Anyone can audit it; nobody — including us — can rewrite it.

Reference

Authentication

One header. Scoped grants.

Every request carries one bearer token. A token holds only the scopes you grant it — issue a read-only analytics token for the warehouse job and a write token for the ingest pipeline, and revoke either one without touching the other.

curl https://saleslab.cloud/api/v1/sessions \
  -H "Authorization: Bearer slt_..."

sessions:readList and read practice and real-call sessions
sessions:writeCreate sessions and ingest real-call recordings
scorecards:readRead scored rubrics and headline results
scenarios:readRead the buyer scenarios behind every call
analytics:readTeam-level rollups, trend series, and outcomes
coaching:readOne-on-one briefs and generated practice loops

Tokens are minted and revoked from Admin → API tokens. Every first use is recorded in the tenant audit log.

Roadmap

What ships next.

Dated, not vague. If a date slips, the changelog says so — see the public roadmap.

Q3 2026
Streaming scorecard endpoint
Server-sent partial results as the rubric scores, instead of one response after hangup.
Q4 2026
Model evaluation harness
Point your own model at our rubric and grade it against the exact bar reps are held to.
2027
Voice-clone-as-a-service
The consented voice pipeline, exposed for callers who never open Sales Lab itself.

Build on the lab

Mint a token. Ship this week.

Five minutes. One scenario. One honest scorecard. The rest of your stack reports on what already happened.

Book a session

What the paid product adds beyond the demo