# TradepilotUSA Requirements Extraction

> TradepilotUSA Requirements Extraction 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).

Extracts structured functional requirements from a source text or project brief, returning itemized requirements with assumptions, evidence gaps, and a human-review flag.

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/requirements_extraction/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-requirements-extraction-71da0bfd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8d2be4N1iQV40Kk8s2at3

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-requirements-extraction-71da0bfd -d '<json body>'
```

Example prompt: Can you extract the functional requirements from this client brief? The audience is our internal project team: 'We need a residential door installation service in Dallas, with consultations Monday through Friday managed by the operations manager, and the installation crew must confirm measurements before starting any job.'

## When to prefer this

Choose this endpoint when you have unstructured text (a project brief, scope document, RFP, or intake form) and need it converted into discrete, numbered functional requirements with explicit assumptions and gap analysis. It is especially useful in procurement, project scoping, or proposal-response workflows where traceability back to the source text matters. Prefer it over general-purpose summarization when you specifically need requirements-format output with human-review flagging.

## Known failure modes

- Source text too short (below 20 characters) — returns validation error
- Brief exceeds 12,000 character limit — request rejected
- Source text exceeds 32,000 character limit — request rejected
- Ambiguous or highly unstructured input may yield low-confidence requirements with many evidence gaps flagged
- Payment failure via x402 protocol — 402 response before processing begins
- Malformed JSON body — 400 bad request

## How this service works

Extract functional and nonfunctional requirements from supplied text, with source references and unresolved ambiguities. 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 task label, a plain-language summary of extracted requirements, a full artifact with numbered functional requirements and their source references, provenance metadata (source, timestamp, whether external research was performed), a request ID, a list of assumptions made during extraction, identified evidence gaps (missing data), and a boolean 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": "requirements_extraction",
  "summary": "Extracted functional requirements include residential door installation in Dallas, consultation scheduling managed by the operations manager Monday through Friday, measurement confirmation by the inst",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n## Functional Requirements\n\n1. **Residential Entry Door Installation Service**\n   - Provide installation of residential entry doors in the Dallas area.\n   - Source: Fictional source document, section 1.\n\n2. **Consultation Scheduling**\n   - Offer consultations Monday through Friday.\n   - The operations manager is responsible for scheduling consultations.\n   - Source: Fictional source document, section 1 and 2.\n\n3. **Measurement Confirmation**\n   - Installation crew must confirm measurements befor",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:42:54.366Z",
   "external_research_performed": false
  },
  "request_id": "example_requirements_extraction",
  "assumptions": [
   "The operations manager and installation crew roles are distinct and responsibilities are as stated.",
   "Consultations are only for residential entry doors and limited to Dallas area."
  ],
  "evidence_gaps": [
   "Current delay rates data.",
   "Final project budget details."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-requirements-extraction-71da0bfd/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)