# TradepilotUSA Process Document

> TradepilotUSA Process Document 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).

Analyzes a source document and generates a structured process draft with steps, inputs, outputs, owners, exception paths, and handoffs tailored to a specified audience

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/process_document/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-process-document-1ac28715
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1LHgTSfEUqfBCPkUx4EaC

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-process-document-1ac28715 -d '<json body>'
```

Example prompt: Can you process this document about how we handle customer onboarding and generate a structured process draft with steps, owners, and exception paths? The audience is our operations team, and here's the brief: 'Improve onboarding efficiency for new SMB clients.' Source text: [paste the 2-page onboarding SOP here].

## When to prefer this

Choose this endpoint when you have unstructured or semi-structured text describing a business workflow and need it converted into a formal, step-by-step process document with defined ownership, exception handling, and handoffs. It is especially useful for ops teams, process improvement initiatives, and onboarding documentation where structure and clarity are critical. Prefer this over general-purpose LLM calls when you need a consistent, structured artifact format with provenance tracking and evidence gap identification built in.

## Known failure modes

- Source text too short (under 20 characters) returns validation error
- Brief too short (under 10 characters) returns validation error
- Source text exceeds 32,000 character limit returns payload too large error
- Audience field exceeds 500 characters returns validation error
- Malformed JSON body returns 400 bad request
- Payment not processed returns 402 payment required
- Service unavailable returns 503 with retry guidance

## How this service works

Convert supplied process notes into steps, inputs, outputs, owners, exception paths, and handoffs. Uses buyer-supplied information only; no external research or outbound actions. Returns a draft for human review.

## Output

Returns a JSON object containing a summary of the generated process, a full artifact with numbered steps (each with inputs, outputs, owner, exception path, and handoff), a list of assumptions made, identified evidence gaps, a provenance block indicating data source and generation timestamp, a unique request ID, and a requires_human_review flag indicating whether manual 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": "process_document",
  "summary": "The draft outlines the residential door installation scheduling process in steps with defined inputs, outputs, owners, exception paths, and handoffs based solely on the supplied fictional example. It ",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n## Process Draft: Residential Entry Door Installation Scheduling Improvement\n\n### Steps\n1. **Initial Consultation Booking**\n   - Schedule weekday consultations with customers.\n   - Input: Customer contact information, preferred consultation date/time.\n   - Output: Confirmed consultation appointment.\n   - Owner: Scheduling Coordinator.\n   - Exception Path: Customer unavailable on proposed dates; reschedule or escalate.\n   - Handoff: Scheduling Coordinator to Consultation Crew.\n\n2. **Consultation ",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:41:42.159Z",
   "external_research_performed": false
  },
  "request_id": "example_process_document",
  "assumptions": [
   "The two-person crew conducts both consultations and installations.",
   "Consultations and installations occur only on weekdays."
  ],
  "evidence_gaps": [
   "Current booking volume data to understand scheduling load.",
   "Customer feedback data to assess satisfaction and identify pain points."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-process-document-1ac28715/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)