Skip to main content
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.

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.
  • 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:
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, passing the version you read as expectedVersion:
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 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. A REST integration can subscribe to pitch_audit.completed instead of polling.

Example conversation

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.