> ## Documentation Index > Fetch the complete documentation index at: https://support.profilebehavior.com/llms.txt > Use this file to discover all available pages before exploring further. # Generate AI Team Summary > Returns a Playbook AI generated Team Summary for multiple profiles up to 40 max. If one has been generated with the current available data already, it simply returns the expected debrief. If new data or a new AI model are available it generates a new debrief with a flag indicating that it is new. ## OpenAPI ````yaml POST /playbook/ai/team-summary openapi: 3.1.0 info: title: Profile Behavior API description: > Unlock actionable behavioral insights for leadership, teamwork, recruiting, and team culture. Profile delivers powerful assessments, analytics, and reporting for businesses, athletic teams, and higher education. For full product information, code samples, and API reference, see our [support documentation](https://support.profilebehavior.com). > **LLMs and AI agents**: See [llms.txt](https://support.profilebehavior.com/llms.txt) for a machine-readable index of all documentation pages. > **MCP connector:** LLM clients (ChatGPT apps, Claude connectors) speak to `/mcp` over streamable HTTP. They discover OAuth automatically via [/.well-known/oauth-protected-resource](https://vanguard.profilebehavior.com/.well-known/oauth-protected-resource), returned in the `WWW-Authenticate` header on any 401. > **Legacy manifests:** - [/.well-known/ai-plugin.json](https://vanguard.profilebehavior.com/.well-known/ai-plugin.json) - [/.well-known/mcp.json](https://vanguard.profilebehavior.com/.well-known/mcp.json) version: 3.0.0 termsOfService: https://profilebehavior.com/legal/terms contact: name: Support url: https://profilebehavior.com/contact email: support@profilebehavior.com x-llm-sitemap: https://support.profilebehavior.com/llms.txt x-documentation-site: https://support.profilebehavior.com x-ai-plugin-manifest: https://vanguard.profilebehavior.com/.well-known/ai-plugin.json x-mcp-manifest: https://vanguard.profilebehavior.com/.well-known/mcp.json x-mcp-endpoint: https://vanguard.profilebehavior.com/mcp x-oauth-protected-resource: https://vanguard.profilebehavior.com/.well-known/oauth-protected-resource servers: - url: https://vanguard.profilebehavior.com/api/v4 security: - M2M: [] - OAuth2: [] tags: - name: test description: Endpoints for testing the API. - name: assessment_invites description: Information on sending invitations to take the assessment. - name: assessments description: Behavioral, leadership, and communication assessment endpoints. - name: accounts description: >- Endpoints for retrieving and managing account and organization information. - name: fixtures description: Endpoints for retrieving fixture data content such as report language. - name: playbook_ai description: Endpoints for generating and retrieving Playbook AI related content. - name: profiles description: Endpoints for individual behavioral profile management. - name: resource_aliases description: >- Endpoints for managing resource alias records that link Profile data to custom defined keys. - name: tags description: >- Endpoints for individual profile tags, categorization, and group management. paths: /playbook/ai/team-summary: post: tags: - playbook_ai summary: Generate an AI Team Summary for multiple profiles. description: > Returns a Playbook AI generated Team Summary for multiple profiles up to 40 max. If one has been generated with the current available data already, it simply returns the expected debrief. If new data or a new AI model are available it generates a new debrief with a flag indicating that it is new. operationId: GenerateAITeamSummary requestBody: content: application/json: schema: type: object properties: profiles: type: array maxItems: 40 description: > An optional array of profile IDs to generate the team summary for. Otherwise, a team summary will be generated with all profiles on the account so long as their are 40 or fewer. items: type: string responses: '200': description: Success content: application/json: schema: allOf: - $ref: '#/components/schemas/Success' - type: object properties: id: type: string description: The ID of the team summary content document. content: type: string description: > The generated team summary meant to help summarize the data of the profiles when taken into context together. example: code: 200 id: 60e9ca73c500a9001534ad84 content: > This team skews high on Influence and Organization, with one very strong Dominance voice and a solid bench of Steadiness and Correctness. Expect energetic dialogue, quick rapport, and a bias to collaborate, balanced by process-minded partners who keep quality high. Communication is split: several are highly talkative and spontaneous, while a few are quiet, analytical contributors who prefer time to think. In DISC terms: the D brings direct, decisive drive (fear: loss of control); many I’s add people-focused energy (fear: being ignored); multiple S’s provide loyalty and patience (fear: instability or change); and the C-leaning members ensure precision and rigor (fear: being wrong or criticized). With Organization scores broadly strong, the group executes well; varied Flexibility and a couple of very low Communication scores mean ideas may concentrate among the loudest unless airtime is structured. Core values cluster around Freedom, Integrity, Responsibility/Order, and Advancement/Power—blending autonomy with high standards and ambition. Several also prize Economic Security and Family Happiness, which pulls toward sustainable pacing and predictable plans. This mix creates a culture that wants room to move, but not at the expense of ethics, clarity, or results. Tensions may surface between Freedom and Order (how much autonomy vs. process), and between Power/Competitiveness and Friendship/Helpfulness; naming these trade-offs will keep motivation high without undercutting cohesion. Under pressure, expect the strong D to press for fast decisions, I’s to seek visibility and rally others, S’s to slow the pace for stability, and C’s to ask for data and risk checks. Most members are emotionally steady, though one or two may spike in reactivity; give them clear roles and support. The upside: resilience, disciplined execution, and strong stakeholder management. The caution: decision whiplash—loud voices racing ahead while steady/precise teammates hesitate. In fast change, S-heavy folks may resist, and I’s can oversell; C’s may stall if standards feel fuzzy. To sharpen performance: 1) Define decision rights and “good enough” criteria up front—pair the D’s speed with C/S guardrails. 2) Run meetings with structured airtime (round-robins, timeboxes) and pre-reads to elevate low-Communication, high-accuracy voices. 3) Protect Freedom through clear guardrails: objectives, boundaries, and check-ins—autonomy inside agreed lanes. 4) Balance ambition with trust: celebrate wins (feeds I/Power), track commitments visibly (reassures S/C and Integrity), and use pilots to de-risk change. 5) In tense moments, use a two-step: quick provisional decision, then a short validation pass for risks and impacts—keeps momentum without sacrificing quality. status: success '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' components: schemas: Success: type: object description: > Standard response object for successful single-resource requests in the Profile Behavior API. Contains an HTTP status code, the returned resource data, and a status indicator. required: - code properties: code: type: integer format: int32 description: HTTP status code of the successful response. status: type: string description: Always "success" for successful responses. enum: - success Error: type: object description: > Standard error response object returned by the Profile Behavior API. Contains a machine-readable error code, a human-readable message, and detailed technical information for debugging or support purposes. required: - code - error - status properties: code: type: integer format: int32 description: HTTP status code associated with the error. error: type: object required: - details - timestamp properties: message: type: string description: A human-readable summary describing the error. timestamp: type: string format: date-time description: ISO 8601 timestamp when the error occurred. status: type: string description: Always "error" for error responses. enum: - error responses: BadRequest: description: Invalid request body content: application/json: schema: $ref: '#/components/schemas/Error' example: code: 400 error: message: Invalid request body timestamp: '2025-01-01T09:42:52.329056-05:00' status: error Unauthorized: description: Unauthorized - authentication required. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: 401 error: message: Invalid token timestamp: '2025-01-01T09:42:52.329056-05:00' status: error securitySchemes: M2M: type: http scheme: bearer OAuth2: type: oauth2 flows: authorizationCode: authorizationUrl: https://login.profilebehavior.com/oauth/authorize tokenUrl: https://login.profilebehavior.com/oauth/token scopes: profiles:read: Read profiles and behavioral summaries (scores, AI debriefs) profiles:write: Create, update, delete profiles and send assessment invites tags:manage: Create, update, delete, and assign tags account:read: Read account details, assessments, and resource aliases account:write: Update account settings and resource aliases description: > OAuth 2.1 authorization code flow with PKCE. Use this whenever your integration acts on behalf of a specific Profile user: third-party apps, AI agents and MCP servers, and any browser-based or CLI tool a user signs in to. Tokens issued under this scheme are scoped to one Profile account (the one the user consented from) and carry OAuth scopes that narrow what the integration can do. Discovery is served at [/.well-known/oauth-protected-resource](/.well-known/oauth-protected-resource). The authorization server is Stytch Connected Apps, which supports Dynamic Client Registration for on-the-fly clients (e.g. MCP agents) in addition to pre-registered integrations. ````