# TradepilotUSA Stakeholder Map Generator

> TradepilotUSA Stakeholder Map Generator is a paid API for AI agents from www.tradepilotusa.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-29).

Analyzes a source text and brief to generate a structured stakeholder map identifying roles, information needs, dependencies, and engagement actions for a given project or initiative.

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/stakeholder_map/execute?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tradepilotusa-stakeholder-map-generator-d7a1e685
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KwwsbKQptl9d37hJ-JArM

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 tradepilotusa-stakeholder-map-generator-d7a1e685 -d '<json body>'
```

Example prompt: I have a project brief and some background text about our door installation scheduling improvement project — can you build a stakeholder map that shows each stakeholder's role, what information they need, their dependencies, and what engagement actions we should take?

## When to prefer this

Choose this endpoint when you need to systematically extract and organize stakeholder information from unstructured text such as project briefs, proposals, or meeting notes into a structured engagement matrix. Prefer this over generic text summarization when the output must explicitly identify roles, dependencies, information needs, and actionable engagement steps. Particularly useful for business operations teams managing projects with multiple internal and external parties.

## Known failure modes

- Source text too short (below 20 character minimum) — returns validation error
- Brief too short (below 10 character minimum) — returns validation error
- Source text exceeds 32,000 character limit — request rejected
- Brief exceeds 12,000 character limit — request rejected
- Insufficient context in brief or source text to identify meaningful stakeholders — may return sparse or assumption-heavy map
- Payment failure or insufficient USDC balance — 402 response, no map generated

## How this service works

Organize supplied stakeholders by project role, information needs, dependencies, and engagement actions. Uses buyer-supplied information only; no external research or outbound actions. Returns a draft for human review.

## Output

Returns a structured JSON object containing a markdown stakeholder table organized by role, information needs, dependencies, and engagement actions. Also includes a summary of the mapping, a list of assumptions made, identified evidence gaps (such as missing data), a provenance record indicating the source and generation timestamp, and a flag indicating whether human review is recommended.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "brief": {
   "type": "string",
   "maxLength": 12000,
   "minLength": 10
  },
  "audience": {
   "type": "string",
   "maxLength": 500
  },
  "source_text": {
   "type": "string",
   "maxLength": 32000,
   "minLength": 20
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "task": "stakeholder_map",
  "summary": "The draft organizes stakeholders for the door installation scheduling improvement project by their roles, information needs, dependencies, and engagement actions. It highlights missing data such as cu",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n### Stakeholder Organization for Door Installation Scheduling Improvement Project\n\n| Stakeholder Role           | Information Needs                                      | Dependencies                             | Engagement Actions                          |\n|----------------------------|-------------------------------------------------------|------------------------------------------|---------------------------------------------|\n| Business Operations Manager | Project scope, vendor proposals,",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:42:22.180Z",
   "external_research_performed": false
  },
  "request_id": "example_stakeholder_map",
  "assumptions": [
   "The business operations manager is the primary decision-maker and coordinator.",
   "Installation crew consists of the two-person team mentioned."
  ],
  "evidence_gaps": [
   "Current booking volume data for scheduling assessment.",
   "Customer feedback regarding current scheduling and consultation experience."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-stakeholder-map-generator-d7a1e685/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.tradepilotusa.com](https://www.zero.xyz/host/www.tradepilotusa.com/llms.txt)