# TradepilotUSA Project Retrospective Analysis

> TradepilotUSA Project Retrospective Analysis 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 project source text to generate a structured retrospective report identifying themes, lessons learned, evidence gaps, and recommendations

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/project_retrospective/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-project-retrospective-analysis-1841474e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fqcPA2pTds_PH2IsSPmnY

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-project-retrospective-analysis-1841474e -d '<json body>'
```

Example prompt: Can you run a project retrospective on our scheduling improvement initiative? The audience is senior operations managers, and here's the full project brief and supporting documentation — I need themes, lessons learned, and any evidence gaps flagged.

## When to prefer this

Choose this endpoint when you need a structured, AI-generated retrospective analysis of a completed project or process, particularly when you have raw source documents (notes, proposals, reports) that need to be synthesized into themed lessons-learned with explicit flagging of assumptions and evidence gaps. Prefer this over generic summarization tools when you need retrospective-specific output structure (themes, evaluation criteria, gaps, human-review flag) aligned with business operations workflows.

## Known failure modes

- Source text too short (minLength 20 characters) or too long (maxLength 32000 characters) — returns validation error
- Brief too short (minLength 10) or too long (maxLength 12000) — returns validation error
- Insufficient or ambiguous source text leads to highly hedged output with many evidence gaps flagged
- Payment not submitted or insufficient USDC — x402 payment required response
- Service unavailable or timeout on large documents — retry recommended

## How this service works

Turn supplied retrospective notes into themes, evidence, lessons, and specific improvement actions. Uses buyer-supplied information only; no external research or outbound actions. Returns a draft for human review.

## Output

Returns a JSON object containing a structured retrospective with a plain-language summary, a formatted markdown artifact document (themes, evaluation criteria, information gaps), a list of assumptions made during analysis, identified evidence gaps, a flag indicating whether human review is required, source provenance metadata, and a unique request ID.

## 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": "project_retrospective",
  "summary": "The retrospective analysis identified key themes around vendor proposals, evaluation criteria, and significant data gaps. Lessons emphasize the need for comprehensive data collection and holistic vend",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n# Retrospective Analysis: Scheduling Improvement Project for Example Door Company\n\n## Themes\n\n1. **Project Scope and Vendor Proposals**\n   - Two vendors proposed different approaches: Vendor A with a process assessment only, Vendor B with assessment plus staff workshop.\n   - Pricing is fictional but indicates a cost difference ($500 vs $800).\n\n2. **Evaluation Criteria**\n   - Implementation effort\n   - Scope clarity\n   - Staff training\n\n3. **Information Gaps**\n   - Lack of current booking volume ",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:41:59.683Z",
   "external_research_performed": false
  },
  "request_id": "example_project_retrospective",
  "assumptions": [
   "The fictional pricing provided is not representative of actual market rates.",
   "The project duration is six weeks as stated."
  ],
  "evidence_gaps": [
   "Current booking volume data for scheduling operations.",
   "Customer feedback related to scheduling experience."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-project-retrospective-analysis-1841474e/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)