# TradepilotUSA Capacity Plan Executor

> TradepilotUSA Capacity Plan Executor is a paid API for AI agents from www.tradepilotusa.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-02).

Generates a structured capacity model framework from a business brief and source text, identifying assumptions, evidence gaps, and a planning artifact.

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/capacity_plan/execute?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tradepilotusa-capacity-plan-executor-ab61fc59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XY9omJDIaupovs-wdw0SR

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-capacity-plan-executor-ab61fc59 -d '<json body>'
```

Example prompt: We run a two-person door installation crew working weekdays in Dallas over a six-week project — can you build a capacity model framework from this brief and flag any missing data we'd need to finalize the plan?

## When to prefer this

Choose this endpoint when you need to rapidly generate a structured capacity planning framework from unstructured business text — particularly for field service, installation, or consulting businesses. It is best suited for situations where some data is available but gaps exist and you want them surfaced explicitly. Prefer alternatives if you need real-time scheduling optimization, integration with live workforce data, or deterministic capacity calculations rather than a generated model framework.

## Known failure modes

- Brief or source_text too short (below minLength) — request rejected with validation error
- Source text exceeds 32,000 character limit — truncation or rejection
- Insufficient business context in brief leads to heavily assumption-laden output with many evidence gaps
- Missing critical inputs (e.g. crew size, duration) results in illustrative/synthetic output rather than grounded plan
- Payment failure via x402 protocol — endpoint returns 402 before processing
- Ambiguous audience field may produce misaligned framing of the capacity model

## How this service works

Build a capacity model from supplied volumes and processing times, showing assumptions and missing inputs. Uses buyer-supplied information only; no external research or outbound actions. Returns a draft for human review.

## Output

Returns a JSON object containing a task label, a plain-language summary of the generated capacity model, a detailed planning artifact (markdown-formatted framework), provenance metadata (source, generation timestamp, whether external research was performed), a request ID, a list of assumptions made during generation, a list of evidence gaps requiring additional data, 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": "capacity_plan",
  "summary": "A capacity model framework was developed based on the supplied example of a two-person installation crew working weekdays over six weeks. Due to missing critical inputs such as consultation and instal",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n## Capacity Model for Door Installation Scheduling Improvement\n\n### Context\nExample Door Company installs residential entry doors in Dallas using a two-person crew and conducts consultations on weekdays. The project aims to improve scheduling over a six-week period.\n\n### Supplied Data\n- Installation crew size: 2 persons\n- Consultation days: Weekdays (assumed Monday to Friday)\n- Project duration: 6 weeks\n- Vendor proposals:\n  - Vendor A: Process assessment for $500\n  - Vendor B: Process assessmen",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:42:16.253Z",
   "external_research_performed": false
  },
  "request_id": "example_capacity_plan",
  "assumptions": [
   "Working days per week are Monday to Friday (5 days).",
   "Working hours per day are 8 hours."
  ],
  "evidence_gaps": [
   "Average consultation duration per customer.",
   "Average installation duration per door."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-capacity-plan-executor-ab61fc59/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)