# Convrgent AI Buying Committee Mapper

> Convrgent AI Buying Committee Mapper is a paid API for AI agents from convrgent.ai, paid per call via x402, $4/call, status unknown (last checked 2026-09-15).

Generates stakeholder-specific sales messaging for each role in a buying committee (2-10 profiles) and predicts deal velocity

## Facts

- Endpoint: POST https://convrgent.ai/api/kyb/committee
- Price: $4/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/convrgent-ai-dd568255
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_srVI7NTSNNPYvERZl0y1l

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability convrgent-ai-dd568255 -d '<json body>'
```

Example prompt: I have a 5-person buying committee at Acme Corp — the CFO is the Decision Maker, our internal champion is the VP of Engineering, there's a skeptical IT Director acting as a Blocker, a procurement Influencer, and 2 End Users from the ops team. Can you generate tailored messaging for each of them and tell me how fast this deal is likely to move?

## When to prefer this

Use this endpoint when you have a multi-stakeholder B2B deal and need coordinated, role-differentiated messaging rather than a single generic pitch. Ideal for enterprise sales scenarios where different committee members (blockers, champions, decision makers) require distinct communication strategies. Prefer this over single-profile messaging endpoints when you need committee-level deal strategy and velocity forecasting in one call.

## Known failure modes

- Fewer than 2 or more than 10 stakeholder profiles provided — returns validation error
- Missing or unrecognized role types for stakeholders — may produce generic rather than role-specific messaging
- Insufficient profile data to generate meaningful personalization — returns low-confidence or generic outputs
- Malformed request payload — returns 400 bad request
- Payment not processed via x402 protocol — returns 402 payment required

## How this service works

Buying Committee Mapper — takes multiple stakeholder profiles (2-10) and generates stakeholder-specific messaging for each role (Decision Maker, Influencer, Champion, Blocker, End User). Coordinated committee strategy with deal velocity prediction.

## Output

Returns stakeholder-specific messaging tailored to each committee role (Decision Maker, Influencer, Champion, Blocker, End User), a coordinated committee-level deal strategy, and a deal velocity prediction estimating how quickly the opportunity is likely to progress.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "bodyType",
    "body",
    "method"
   ],
   "properties": {
    "body": {
     "required": [
      "product",
      "stakeholders"
     ],
     "properties": {
      "product": {
       "type": "string",
       "description": "Description of what you're selling"
      },
      "stakeholders": {
       "type": "array",
       "items": {
        "type": "object"
       },
       "description": "Array of 2-10 stakeholder profiles with role + personality data"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mode": "multi-stakeholder",
  "risk_factors": [
   "IT veto on security grounds",
   "CFO budget freeze"
  ],
  "per_stakeholder": [
   {
    "role": "CFO",
    "key_concern": "hidden costs",
    "pitch_angle": "3-year TCO comparison",
    "win_condition": "clear ROI model"
   },
   {
    "role": "VP Sales",
    "key_concern": "adoption timeline",
    "pitch_angle": "pipeline velocity gains",
    "win_condition": "quick wins demo"
   },
   {
    "role": "IT Director",
    "key_concern": "integration complexity",
    "pitch_angle": "security architecture",
    "win_condition": "sandbox trial"
   }
  ],
  "meeting_sequence": [
   "1:1 with IT Director (technical deep-dive)",
   "Demo for VP Sales (results focus)",
   "Executive summary for CFO"
  ],
  "committee_dynamics": {
   "blocker": "IT Director",
   "champion": "VP Sales",
   "influence_map": "...",
   "decision_maker": "CFO"
  },
  "consensus_strategy": "Secure IT sign-off first (removes blocker), arm VP Sales with quick-win data (builds momentum), present unified ROI to CFO (closes)"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/convrgent-ai-dd568255/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from convrgent.ai](https://www.zero.xyz/host/convrgent.ai/llms.txt)