# TradepilotUSA Meeting Brief Generator

> TradepilotUSA Meeting Brief Generator 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).

Generates a structured meeting brief document from source text and audience context to prepare for a business meeting or discovery session

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/meeting_brief/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-meeting-brief-generator-66814d85
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3BfrsmL3evBZYpixluZPf

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-meeting-brief-generator-66814d85 -d '<json body>'
```

Example prompt: Can you put together a meeting brief for my upcoming discovery call with the operations manager at Acme Roofing — the source material is their last three support tickets about scheduling issues, and the audience is our sales consultant going into the meeting cold.

## When to prefer this

Choose this endpoint when you need to quickly synthesize raw notes, emails, or documents into a structured, stakeholder-ready meeting brief before a discovery or business meeting. It is especially useful when the audience has no prior context and needs background, assumptions, and open questions surfaced automatically. Prefer this over generic summarization tools when the output needs to be formatted as a professional meeting prep document with explicit evidence gaps and human-review flags.

## Known failure modes

- Source text too short (below 20 characters) returns validation error
- Brief description too short (below 10 characters) returns validation error
- Source text exceeds 32,000 character limit causing rejection
- Brief exceeds 12,000 character limit causing rejection
- Ambiguous or very sparse input may produce low-quality brief with many evidence gaps
- Network or payment failure returns 402 or 5xx error

## How this service works

Produce a meeting brief with supplied background, desired outcomes, agenda, questions, and likely objections. 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 meeting brief, a detailed markdown artifact document with background, discussion points, and context, a list of assumptions made, identified evidence gaps, provenance metadata (source and generation timestamp), a request ID, 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": "meeting_brief",
  "summary": "This meeting brief prepares for a discovery discussion with the operations manager of Example Door Company to address missed consultation appointments and explore a scheduling-process assessment. It o",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n# Meeting Brief: Consultation Scheduling Improvement for Example Door Company\n\n## Background\nExample Door Company specializes in installing residential entry doors in Dallas, utilizing a two-person crew for installations. The operations manager has identified challenges with consultation scheduling, specifically missed appointments, and is interested in exploring improvements. A discovery meeting is planned to discuss these issues and the potential effort required to implement any changes.\n\n## D",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:39:41.033Z",
   "external_research_performed": false
  },
  "request_id": "example_meeting_brief",
  "assumptions": [
   "The operations manager is the primary decision-maker or key stakeholder for consultation scheduling improvements.",
   "Missed appointments are a significant pain point impacting operations and customer satisfaction."
  ],
  "evidence_gaps": [
   "Details on the current consultation scheduling process workflow.",
   "Specific reasons and frequency of missed appointments."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-meeting-brief-generator-66814d85/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)