> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwairy.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Run a Pitch Audit for a prospect with MCP

> Create a Pitch Audit from an MCP assistant, review and save its prompts, confirm the credit use with a token, then read the finished prospect report.

Prepare a prospect audit from a conversation: the assistant creates the audit and prepares prompts, you review them, and you confirm before any credit is used. This guide uses MCP. The REST API offers the same lifecycle in [Create a Pitch Audit](https://docs.qwairy.co/developers/endpoints/pitch-audits/create.md).

## Before you start

* An agency team on an active Business, Agency Business or Enterprise plan. Pitch Audit write tools are not available otherwise.
* A Manager or Owner role in the agency team.
* A connection with the `write:pitch-audits` scope for the write tools and `read:pitch-audits` to read the audit. See [OAuth authentication](https://docs.qwairy.co/mcp/oauth.md).
* Credits for the audit. The preview shows the amount before you confirm.

## Steps

**1. Find your agency team**

Ask the assistant for the team ID. `list_brands` returns it in each workspace's `team` object. Earlier audits returned by `list_pitch_audits` also show their workspace.

**2. Create the audit**

The assistant calls [`create_pitch_audit`](https://docs.qwairy.co/mcp/write/pitch-audits#create_pitch_audit):

```json theme={null}
{
  "teamId": "team_agency_01",
  "url": "prospect.example",
  "name": "Prospect Co",
  "countryCode": "US",
  "promptCount": 20
}
```

Qwairy prepares the prompts and uses no credits at this stage. Leave `autoStartResponses` unset: it skips the prompt review.

**3. Wait for the review state**

The assistant reads the audit with `list_pitch_audits` until its status is `AWAITING_PROMPTS`, then opens it with `get_pitch_audit`. The report returns the prompts and the audit `version`.

**4. Review and save the prompts**

Read the prompts with the assistant. Remove or rewrite the ones that do not fit the prospect, then save the full list with [`save_pitch_audit_prompts`](https://docs.qwairy.co/mcp/write/pitch-audits#save_pitch_audit_prompts), passing the `version` you read as `expectedVersion`:

```json theme={null}
{
  "auditId": "audit_01",
  "expectedVersion": 4,
  "prompts": [
    { "id": "p1", "text": "Which analytics tools suit a ten-person operations team?", "category": "TOFU", "topic": "Analytics tools" },
    { "id": "p2", "text": "How does Prospect Co compare with other analytics vendors?", "category": "MOFU", "topic": "Vendor comparison" }
  ]
}
```

The call replaces the whole prompt set. A version conflict means the audit changed: read it again.

**5. Preview the cost**

Ask the assistant to call [`confirm_pitch_audit`](https://docs.qwairy.co/mcp/write/pitch-audits#confirm_pitch_audit) with `dryRun` set to `true`, or call it without a token. Qwairy returns the credits the audit will use, any warnings, and a `confirmationToken`. Nothing has started.

**6. Confirm**

If the cost is acceptable, approve it. The assistant calls `confirm_pitch_audit` again with the same arguments and the token. The token is single use and valid for 10 minutes, and it is rejected if the prompts or the cost changed since the preview. Your MCP client may also ask for its own approval.

**7. Read the report**

Poll `get_pitch_audit` until the status is `COMPLETED`. To compare a co-competitor, reuse a `subjectId` from `coCompetitors`. See [Pitch Audit read tools](https://docs.qwairy.co/mcp/tools/pitch-audits.md). A REST integration can subscribe to [`pitch_audit.completed`](https://docs.qwairy.co/developers/integration-webhooks/events#pitch_audit-completed) instead of polling.

## Example conversation

```text theme={null}
You: Prepare a Pitch Audit for prospect.example, 20 prompts, US market.

Assistant: creates the audit and reports that it is waiting for prompt review.

You: Drop the two prompts about careers, then show me the cost.

Assistant: saves 18 prompts, then previews the confirmation: the credits the
audit will use and a confirmation token. Nothing has started.

You: Confirm.

Assistant: confirms with the token. Answer collection starts. Later, the
assistant reads the finished report.
```

## Limits

* Retrying a failed audit and exporting a report remain dashboard actions.
* Content from the prospect website can reach the assistant through the report. Read previews before you confirm. See [Security](https://docs.qwairy.co/mcp/write/overview.md#security).

## Related

* [Pitch Audit write tools](https://docs.qwairy.co/mcp/write/pitch-audits.md)
* [Pitch audits for agencies](https://docs.qwairy.co/agencies/pitch-audits.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.