# TradepilotUSA Risk Register Generator

> TradepilotUSA Risk Register 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-10-02).

Analyzes a project brief and source text to generate a structured risk register with identified risks, likelihoods, impacts, mitigations, assumptions, and evidence gaps.

## Facts

- Endpoint: POST https://www.tradepilotusa.com/api/agent-commerce/v1/services/risk_register/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-risk-register-generator-d1af8eaf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hRtwPt57YpmSGaJaNRboM

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-risk-register-generator-d1af8eaf -d '<json body>'
```

Example prompt: Can you generate a risk register for our door installation scheduling improvement project? Here's the project brief: we want to reduce booking delays by 30% over six weeks, but we don't have baseline data yet and are evaluating three vendors. The audience is our operations management team.

## When to prefer this

Choose this endpoint when you need a structured, formatted risk register document generated from a project brief or planning text, especially for business operations, IT, construction, or service delivery projects. It is well-suited for situations where you want risks categorized by likelihood and impact with mitigations, assumptions, and evidence gaps explicitly called out. Prefer this over generic LLM prompting when you need consistent, structured output with provenance metadata and a human-review flag.

## Known failure modes

- Brief or source_text too short (below minLength) returns validation error
- Source text or brief exceeds maxLength limits causing rejection
- Vague or ambiguous brief may produce generic or low-quality risk register
- Missing source_text may result in incomplete risk identification
- Payment failure via x402 protocol returns 402 before processing begins
- Service unavailability returns 5xx error

## How this service works

Identify risks grounded in the supplied project brief, with likelihood rationale, impact, mitigations, and owners. 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 prose summary of key risks, a detailed artifact (formatted risk register markdown with identified risks, likelihood ratings, impact assessments, and mitigations), a list of assumptions made, identified evidence gaps, a flag indicating whether human review is required, and a unique request ID with provenance metadata.

## 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": "risk_register",
  "summary": "Key risks include lack of baseline operational data, unclear vendor scope, limited staff training, scheduling constraints, and budget uncertainties. Mitigations focus on data collection, scope clarifi",
  "artifact": "Illustrative excerpt from a synthetic provider check:\n## Risk Identification for Door Installation Scheduling Improvement Project\n\n### 1. Incomplete Data on Current Operations\n- **Likelihood:** High\n  - Rationale: The brief explicitly states that current booking volume, customer feedback, vendor references, and measured outcomes are unknown.\n- **Impact:** High\n  - Without baseline data, assessing improvement impact and vendor effectiveness is difficult, risking poor decision-making.\n- **Mitigations:**\n  - Collect baseline data on booking volume, cu",
  "provenance": {
   "source": "buyer_supplied",
   "generated_at": "2026-09-22T14:41:48.915Z",
   "external_research_performed": false
  },
  "request_id": "example_risk_register",
  "assumptions": [
   "Vendor proposals are final and no further negotiation is planned.",
   "The project timeline is fixed at six weeks."
  ],
  "evidence_gaps": [
   "Current booking volume and scheduling data.",
   "Customer feedback on current scheduling and service."
  ],
  "requires_human_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tradepilotusa-risk-register-generator-d1af8eaf/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)