Developers

Deliver Approved Messaging As Structured Product Data

The Message Schema Console holds the JSON Message Source and request params — audience, channel, character_limit, claim_policy — on the left, live validation in the center, and rendered Hero, Sales, Banner, Partner, and Ad copy on the right, always from one object.

1 · Message Source JSON + request params

{
  "message_source": {
    "id": "SP-SRC-07",
    "version": "1.4",
    "category": "AI operations platform",
    "audience": "Support teams at mid-market and enterprise companies",
    "problem": "Complex cases lose customer context across handoffs",
    "outcome": "Resolve complex cases without losing customer context",
    "differentiator": "Context persists across every handoff"
  },
  "request": {
    "audience": "developer",
    "channel": "hero",
    "character_limit": 160,
    "claim_policy": "approved-only"
  }
}

2 · Validation

Category field present
Audience field present
Differentiator field present
No banned terms found
claim_policy enforced on render
Evidence attached to Outcome

1 warning — Outcome field has no attached evidence citation.

3 · Live render preview

Hero

“An AI operations platform that helps support teams resolve complex cases without losing customer context.”

Sales

“SloganPrism — an AI operations platform built for support teams handling complex, high-context cases.”

Banner

“This case keeps its full context across every handoff.”

Partner

“An AI operations platform your customers can add on top of their existing support stack.”

Ad (Claim)

“Cut response time in half.”

Edit the JSON — validation and all five rendered surfaces update together from the same Message Source object. Set claim_policy to "approved-only" and the Ad render blocks any claim without Claim Library approval.

API documentation · Webhooks · Integrations

API documentation

Message Source and claim endpoints

REST reference for the Message Source object, claim library, channel formats, drift events, and recall test runs.

GET  /v1/message-source
POST /v1/message-source/validate
GET  /v1/claims
POST /v1/claims/load-test
GET  /v1/channel-packs
POST /v1/drift/check
POST /v1/recall-tests
POST /v1/events/test

source.approved — A Message Source version is approved
claim.flagged — A claim breaks a Claim Load Test pillar
drift.detected — A channel's category term diverges from the source
format.generated — A channel pack is generated for a claim set
recall.completed — A five-second recall test run finishes

Integrations

NotionMessage Source pages
Google DocsBrand and positioning docs
FigmaDesign copy layers
WebflowLive website content
ContentfulCMS-managed marketing pages
HubSpotLanding pages and email copy
SlackDrift and approval alerts
Custom CMSSigned webhook read/write