# TradepilotUSA Sales Handoff Executor

> TradepilotUSA Sales Handoff 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 sales handoff deliverable — including a summary, artifact, assumptions, and evidence gaps — from a provided brief and source text, flagged for human review.

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/sales_handoff/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-sales-handoff-executor-4b187bfe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QyRiVwh3kTIvXM3HMfezi

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-sales-handoff-executor-4b187bfe -d '<json body>'
```

Example prompt: Take this prospect brief about Example Door Company — they need help improving their consultation scheduling process to reduce missed appointments — and generate a formal sales handoff document with a summary, delivery requirements, assumptions, and evidence gaps. The audience is the operations manager.

## When to prefer this

Choose this endpoint when you need to convert unstructured prospect notes, call transcripts, or client briefs into a structured, human-reviewable sales handoff document — especially when the handoff must include delivery requirements, explicit assumptions, and flagged evidence gaps. It is purpose-built for sales-to-operations transitions within the TradepilotUSA workflow ecosystem, and is preferable over generic document generation when you need provenance tracking and a human-review flag baked into the output.

## Known failure modes

- Brief or source_text too short (below minLength) — validation error returned
- Source text exceeds 32,000 character limit — request rejected
- Brief exceeds 12,000 character limit — request rejected
- Insufficient context in brief to generate meaningful assumptions — low-quality artifact with many evidence gaps
- Payment failure or insufficient USDC balance — 402 response, no artifact generated
- Malformed JSON body — 400 bad request

## How this service works

Convert supplied deal notes into delivery requirements, commitments, ownership, open questions, and acceptance criteria. 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 prose summary of the deliverable, a detailed handoff artifact (delivery requirements and context), a provenance block (source, timestamp, whether external research was performed), the original request ID, a list of assumptions made, identified evidence gaps, and a boolean flag indicating whether human review is required before acting on the output.

## 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": "sales_handoff",
  "summary": "The deliverable is a scheduling-process assessment for Example Door Company focused on improving consultation scheduling and reducing missed appointments. It includes conducting a discovery meeting, a",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n## Delivery Requirements\n\n- Conduct a discovery meeting with the operations manager of Example Door Company to discuss current consultation scheduling challenges, specifically focusing on missed appointments.\n- Assess the existing scheduling process used by the two-person installation crews for residential entry doors in Dallas.\n- Identify potential areas for improvement in scheduling efficiency and reliability.\n- Document the findings and provide recommendations for process enhancements.\n\n## Co",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:40:39.205Z",
   "external_research_performed": false
  },
  "request_id": "example_sales_handoff",
  "assumptions": [
   "The discovery meeting is the initial step before any implementation effort.",
   "No implementation or savings guarantees are part of this deliverable."
  ],
  "evidence_gaps": [
   "Budget allocated for the assessment and any future implementation.",
   "Expected timeline or purchase date for follow-up services."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-sales-handoff-executor-4b187bfe/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)