Optimize and Deploy API: Audit, Rewrite, Publish

One endpoint to rule them all

The Optimize and Deploy API lets you run a multi-stage pipeline that audits your pages, optimizes their content for AI search visibility, and optionally stages or deploys the results to AXP — all from a single API call. One endpoint to bind your audit, optimization, staging, and deployment workflows together. Each pipeline is asynchronous. You submit URLs, receive tracking tokens, and then poll for status or receive webhook callbacks as each stage completes.

The Optimize and Deploy API is currently in early access and available on request. Contact your Customer Success representative to get access enabled for your organization.

How it works

The pipeline chains three Scrunch products together. Each stage is optional — use only what you need.

Product	Pipeline stage	What it does	Required?
Site Audit	`audit`	Evaluates AI discoverability: robots.txt, bot access, content quality, content delivery	Always runs
Content Optimizer	`optimizing`	Rewrites page content to improve AI visibility for target prompts and personas	Set `optimize: true`
AXP (stage only)	`optimizing` → `completed`	Stages optimized content on your AXP site without publishing it live	Set `stage_axp: true` + `site_id`
AXP (deploy live)	`deploying`	Publishes optimized content to your AXP site as a new live version	Set `deploy_axp: true` + `site_id`

Configuration per product

Each product in the pipeline has its own configuration:

Site Audit — runs automatically on each URL, no extra config needed
Content Optimizer — optionally configure target_prompts, target_personas, target_sources, and override_suggestions at the batch level or per-URL
AXP — requires a site_id (the RegisteredSite ULID). All URLs must belong to the site’s domain. Use stage_axp: true to stage content for review without going live, or deploy_axp: true to publish a new live version. The two flags are mutually exclusive.

Pipeline stages

Every URL you submit moves through these stages in order:

Stage	`orchestration_status`	What happens
Audit	`audit`	Page is fetched and evaluated for AI discoverability (robots.txt, content quality, bot access)
Optimize	`optimizing`	Content is analyzed and rewritten to improve AI visibility for your target prompts and personas. If `stage_axp: true`, the optimized content is also staged to AXP during this stage.
Deploy	`deploying`	Optimized content is published to AXP as a new live version
Done	`completed`	All stages finished successfully
Error	`failed`	Pipeline stopped at the failing stage

The optimize and deploy stages only run if you set optimize: true and deploy_axp: true in the request. With defaults, only the audit stage runs. Set stage_axp: true instead of deploy_axp: true when you want optimized content staged on AXP for review without going live.

When to use it

You want to audit, optimize, and deploy pages without multiple API calls
You need batch processing across many URLs
You want webhook notifications when stages complete
You’re building automated content optimization pipelines

When not to use it

You only need audit results — use the Site Audit API directly
You want to query existing visibility data — use the Query API
You need manual control over each optimization — use the Scrunch dashboard

Request patterns

Simple: list of URLs

Pass urls when every URL should use the same optimization configuration:

curl -X POST "https://api.scrunchai.com/v2/orchestration/optimize-and-deploy/1234" \
  -H "Authorization: Bearer $SCRUNCH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://example.com/page-a",
      "https://example.com/page-b"
    ],
    "optimize": true,
    "deploy_axp": true,
    "site_id": "01JEXAMPLE00000000000000"
  }'

Detailed: per-URL overrides

Pass requests when individual URLs need different prompts, personas, or sources:

curl -X POST "https://api.scrunchai.com/v2/orchestration/optimize-and-deploy/1234" \
  -H "Authorization: Bearer $SCRUNCH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requests": [
      {
        "url": "https://example.com/page-a",
        "target_prompts": ["best budget airlines"],
        "target_personas": [{"name": "Budget Traveler"}]
      },
      {
        "url": "https://example.com/page-b",
        "target_prompts": ["luxury travel options"]
      }
    ],
    "optimize": true,
    "deploy_axp": true,
    "site_id": "01JEXAMPLE00000000000000"
  }'

Provide either urls or requests, not both. The API will reject requests that include both fields.

Stage to AXP without going live

Use stage_axp: true to run audit + optimize + stage content to AXP without publishing a live version. This is useful when you want to review optimized content in the Scrunch dashboard before manually deploying it.

curl -X POST "https://api.scrunchai.com/v2/orchestration/optimize-and-deploy/1234" \
  -H "Authorization: Bearer $SCRUNCH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://example.com/page-a",
      "https://example.com/page-b"
    ],
    "optimize": true,
    "stage_axp": true,
    "site_id": "01JEXAMPLE00000000000000"
  }'

The pipeline ends in orchestration_status: completed once content is staged. The response includes an optimization_run_id, but axp_version_id stays null because no live version is published.

Flags	Pipeline result
`optimize: true`	Audit + optimize. Optimization markdown saved on the run, AXP untouched.
`optimize: true`, `stage_axp: true`, `site_id`	Audit + optimize + stage to AXP. No live deploy. Review and deploy from the dashboard.
`optimize: true`, `deploy_axp: true`, `site_id`	Audit + optimize + stage + publish a new live AXP version.

stage_axp and deploy_axp are mutually exclusive — passing both returns a 422 validation error. stage_axp: true also requires optimize: true and a valid site_id whose AXP integration is active.

Tracking progress

Each URL gets its own tracking token. Use it to poll for status:

curl "https://api.scrunchai.com/v2/orchestration/optimize-and-deploy/1234/01JABCTOKEN00000000000" \
  -H "Authorization: Bearer $SCRUNCH_API_KEY"

The response includes the current orchestration_status, timestamps, and result data as it becomes available. For real-time updates without polling, configure webhooks to receive callbacks at each stage transition.

Set up webhooks

Get notified when audits, optimizations, and deployments complete.

Error codes

When a pipeline fails, the response includes a structured error code. Use these to identify what went wrong and where:

Prefix	Stage	Example codes
`ORCH-INIT`	Initialization	Invalid URL, missing site_id, domain mismatch, quota exceeded
`ORCH-AUDIT`	Audit	Fetch failed, timeout, page not found
`ORCH-OPT`	Optimization	No content to optimize, LLM failure, source fetch failed
`ORCH-DEPLOY`	Deployment	Site not found, AXP publish failed
`ORCH-HOOK`	Webhook delivery	Delivery failed, SSRF blocked, timeout

Each error includes a human-readable message and a short error_hash you can reference when contacting support.

Relationship to other Scrunch products

The Optimize and Deploy API is a composition layer that chains together three standalone Scrunch products:

Site Audit is always the first stage. It runs the same checks as POST /{brand_id}/page-audits.
Content Optimizer uses audit results plus your target prompts and personas to generate optimized content.
AXP deploys the optimized content as a new version to your registered site.

Each product can also be used independently outside of this pipeline.

Dashboard visibility

Everything the pipeline does is fully visible in the Scrunch dashboard — audit results, optimization runs, and AXP deployments all appear in their respective pages exactly as if they had been performed manually. AXP deployments are tracked in the Version History with full change tracking, and you can compare original vs. optimized content side by side.

Run your first pipeline

Go to the Optimize and Deploy Quickstart

Query API

Responses API

Agent Traffic API

AI Referrals API

Site Audit API

Signals API

Sitemap API

Collection API

AXP Render API

Optimize & Deploy API

Webhooks

Configuration API

Optimize and Deploy API: Audit, Rewrite, Publish

One endpoint to rule them all

How it works

Configuration per product

Pipeline stages

When to use it

When not to use it

Request patterns

Simple: list of URLs

Detailed: per-URL overrides

Stage to AXP without going live

Tracking progress

Set up webhooks

Error codes

Relationship to other Scrunch products

Dashboard visibility

Run your first pipeline

​One endpoint to rule them all

​How it works

​Configuration per product

​Pipeline stages

​When to use it

​When not to use it

​Request patterns

​Simple: list of URLs

​Detailed: per-URL overrides

​Stage to AXP without going live

​Tracking progress

Set up webhooks

​Error codes

​Relationship to other Scrunch products

​Dashboard visibility

Run your first pipeline

One endpoint to rule them all

How it works

Configuration per product

Pipeline stages

When to use it

When not to use it

Request patterns

Simple: list of URLs

Detailed: per-URL overrides

Stage to AXP without going live

Tracking progress

Error codes

Relationship to other Scrunch products

Dashboard visibility