Skip to content

DISC Profile

Retrieve a normalized DISC psychometric profile for a user within your organization.

This endpoint is designed to:

  • abstract away DISC provider complexity
  • return a stable, tool-friendly structure
  • integrate cleanly with downstream reasoning tools (such as Advice)

SotsAI acts as a stateless proxy: profiles are fetched on demand and not stored.


Use this endpoint when:

  • your organization relies on DISC profiles managed by SotsAI
  • your orchestration layer needs DISC scores (e.g., on cache miss or after invitation completion)
  • you want to avoid handling DISC provider logic yourself

You typically call this before:

  • generating behavioral advice
  • adapting communication strategies
  • running DISC-aware reasoning in your LLM pipeline

If you already manage DISC profiles internally, you do not need this endpoint — you can bring your own profile instead.


For a given user in your organization, SotsAI:

  1. Derives a deterministic provider lookup identifier from (org + one-way encrypted email)
  2. Fetches their DISC results from the configured provider
  3. Normalizes scores into a consistent DISC format
  4. Returns the profile without persisting it

This guarantees:

  • no vendor-specific formats
  • no storage of psychometric data
  • deterministic behavior across calls

The email address of the user whose DISC profile should be fetched.

This email is used only to derives a deterministic provider lookup identifier from (org + one-way encrypted email).

Language context used when interacting with the underlying DISC provider.

This does not affect score computation, only provider-side behavior.


{
"email": "user@company.com",
"locale": "en"
}

The response contains a normalized DISC profile, ready to be passed directly into SotsAI reasoning tools.

  • tool: Identifies the psychometric framework ("disc")
  • raw_scores: Provider-derived DISC scores, grouped by:
    • natural: the user’s natural (baseline) DISC style
    • adapted: the user’s adapted (contextual) DISC style

Scores are expressed on a 0–100 scale for each DISC dimension:

  • D — Dominance
  • I — Influence
  • S — Steadiness
  • C — Conscientiousness

{
"tool": "disc",
"raw_scores": {
"natural": {
"D": 72,
"I": 58,
"S": 34,
"C": 46
},
"adapted": {
"D": 65,
"I": 52,
"S": 40,
"C": 55
}
}
}

A common pattern:

  1. Fetch the DISC profile
  2. Inject it into a reasoning request (i.e. Advice)
  3. Let your LLM render the final output

Example (conceptual):

DISC Profile → Behavioral Reasoning → Natural Language Response

You should treat the returned profile as input data, not as something to interpret directly for the end user. You can pass the output object as-is into SotsAI reasoning tools:

{
"context_summary": "...",
"user_profile": {
"tool": "disc",
"raw_scores": {
"natural": { "...": "..." },
"adapted": { "...": "..." }
}
}
}

  • Profiles are fetched on demand
  • No data is stored by SotsAI
  • No personal identifiers are returned in the response
  • All access is scoped to your organization

  • Requests are authenticated via your organization API key
  • Calls DO NOT count toward your monthly quota
  • rate limit exists

Typical error cases include:

  • profile not found for the user
  • invalid or inactive organization
  • unexpected provider or processing errors

Error responses are stable and machine-readable.


This endpoint gives you:

  • a clean, normalized DISC profile
  • no vendor lock-in at the API level
  • zero storage or lifecycle management on your side
  • seamless integration with SotsAI’s reasoning tools

Call this from your backend/orchestration layer only. Do not expose API keys or user emails to browsers or untrusted clients.