Funnels

Point a real hostname the organization owns (e.g. offers.acme.com) at a funnel and register it for a public TLS certificate. This publishes the funnel on a NEW address on the open internet as soon as the tenant's CNAME resolves. Returns the DNS record they must create; use funnel_domains.verify afterwards.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_domains.attach \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain": "example"
  }'

Over MCP the same operation is the tool funnel_domains_attach at https://app.chirply.io/api/mcp, same bearer token, same input.

Disconnect a custom domain and release its Cloudflare hostname and certificate. Everything served on that address STOPS immediately — the funnel, any single pages, and every LinkWizard link hosted on it, including copies already shared. The funnel itself, its /f/<slug> URL, and the links themselves are kept and can be moved elsewhere.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_domains.detach \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "domain_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_domains_detach at https://app.chirply.io/api/mcp, same bearer token, same input.

List the custom domains connected to the organization's funnels, with their verification and TLS status and the CNAME record the tenant has to create.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_domains.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnel_domains_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Re-check a connected domain with Cloudflare and update its status. Run this once the CNAME record exists — certificate issuance is asynchronous and completes on its own within a few minutes.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_domains.verify \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "domain_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_domains_verify at https://app.chirply.io/api/mcp, same bearer token, same input.

Apply a natural-language change to a page's draft document ("make the headline punchier", "add a testimonial section") and RETURN the new document — nothing is saved, so pass it to funnel_pages.save_content to keep it. The pre-edit document is snapshotted automatically. If the instruction implies a restyle, the funnel's theme IS changed immediately — that write is not held back for review, and it restyles every page of the funnel including any already published. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.ai_edit \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "instruction": "example"
  }'

Over MCP the same operation is the tool funnel_pages_ai_edit at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the native editor's actual component fields, defaults, layout slots and limits. Use this contract to create fully editable documents. No custom code is executed and no model is called.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.component_schema \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "component": "example"
  }'

Over MCP the same operation is the tool funnel_pages_component_schema at https://app.chirply.io/api/mcp, same bearer token, same input.

Add a page to the end of a funnel, seeded with a ready-made starter layout for the chosen step type. It is created as a draft; publish it separately with funnel_pages.publish.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool funnel_pages_create at https://app.chirply.io/api/mcp, same bearer token, same input.

PERMANENTLY DESTROY a page, its live content and its entire version history. This cannot be undone. The home page cannot be deleted — it is the funnel's entry point; delete the funnel instead.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Use AI to write and design a complete new page, then append it to an existing funnel or website as a private DRAFT. It does not publish the page and contacts nobody. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.generate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example",
    "prompt": "example"
  }'

Over MCP the same operation is the tool funnel_pages_generate at https://app.chirply.io/api/mcp, same bearer token, same input.

Generate a complete page document from a prompt and RETURN it for review — no page is created or changed. Pass the result to funnel_pages.save_content to keep it. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.generate_content \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "prompt": "example"
  }'

Over MCP the same operation is the tool funnel_pages_generate_content at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one page with BOTH documents: `content` is the working draft you edit, `published_content` is what visitors currently see. Read this before editing a page — funnel_pages.save_content expects a document in the same shape.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List a funnel's pages in step order. Page documents are omitted — call funnel_pages.get for a page's content.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_list at https://app.chirply.io/api/mcp, same bearer token, same input.

List a page's saved restore points, newest first — every publish, every AI edit, and every manual snapshot. Documents are omitted; funnel_pages.restore_version brings one back.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.list_versions \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_list_versions at https://app.chirply.io/api/mcp, same bearer token, same input.

Apply an atomic batch of native component operations to a page draft with revision checking and an automatic restore point. Nested slots and property paths are supported. A failed operation or stale revision rejects the entire batch. Nothing is published and no AI is called.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.patch \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "expected_revision": "example",
    "operations": [
      null
    ]
  }'

Over MCP the same operation is the tool funnel_pages_patch at https://app.chirply.io/api/mcp, same bearer token, same input.

PUT THIS PAGE ON THE PUBLIC INTERNET. Copies the working draft over the live version, so whatever the draft currently says becomes what visitors see at /f/<slug>/<path>. If the funnel itself is still a draft it is published too, because a live page inside an offline funnel is unreachable. A restore point is saved first, so this is undoable via funnel_pages.restore_version.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.publish \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_publish at https://app.chirply.io/api/mcp, same bearer token, same input.

Set the order visitors move through a funnel's steps. Pass every page id of the funnel in the order you want; the first one must be the funnel's home page. Order only — no content or URL changes.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.reorder \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "page_ids": [
      "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
    ]
  }'

Over MCP the same operation is the tool funnel_pages_reorder at https://app.chirply.io/api/mcp, same bearer token, same input.

Bring a saved version back into the page's WORKING DRAFT. The live page is not touched — publish afterwards if you want visitors to see it. The draft being replaced is snapshotted first, so a restore is itself undoable.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.restore_version \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "version_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_restore_version at https://app.chirply.io/api/mcp, same bearer token, same input.

Save a strictly validated native page document as the working draft. Invalid components and props are rejected with paths, never discarded. The prior draft is snapshotted atomically. Pass expected_revision from the last read to reject stale writes. Live visitors keep the published snapshot.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.save_content \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "document": {}
  }'

Over MCP the same operation is the tool funnel_pages_save_content at https://app.chirply.io/api/mcp, same bearer token, same input.

Make a published page send visitors somewhere else instead of rendering. Takes effect after the next publish, on every address it is served at, including the funnel's custom domain. The page's content is kept untouched — pass an empty redirect_url to switch it back on. Works on the home page too, which is how a whole single-page site gets redirected.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.set_redirect \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "redirect_url": "https://example.com"
  }'

Over MCP the same operation is the tool funnel_pages_set_redirect at https://app.chirply.io/api/mcp, same bearer token, same input.

Save a named restore point for a page. Nothing about the page changes — this only records what the draft looks like now so it can be brought back later.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.snapshot \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_snapshot at https://app.chirply.io/api/mcp, same bearer token, same input.

Take one live page off the public internet — visitors on its URL immediately stop being able to reach it. The rest of the funnel stays live. The draft and the last published content are kept, so publishing again restores it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.unpublish \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_unpublish at https://app.chirply.io/api/mcp, same bearer token, same input.

Rename a page, change its draft URL path, or change its step type with revision checking. Path changes update the site's native draft links, redirects and shared sections together, and require whole-site publication. Live content keeps its old routes until then. Publishing moves the public URL; external inbound links require an explicit redirect. Pause running A/B tests before renaming routes. The home page remains fixed at the site root.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Save a page's search title, meta description, canonical URL, social image, and search-index visibility. This changes metadata on the working page record; published pages retain their metadata until the next publish.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.update_seo \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_pages_update_seo at https://app.chirply.io/api/mcp, same bearer token, same input.

Check a proposed native document against the same strict field and layout contract used by saves and publishing. Returns precise issues without removing unsupported content. No page changes or paid calls occur.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_pages.validate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "document": null
  }'

Over MCP the same operation is the tool funnel_pages_validate at https://app.chirply.io/api/mcp, same bearer token, same input.

PERMANENTLY DESTROY one of the organization's saved funnel templates, including every page document frozen inside it. This cannot be undone. Funnels already built from it are unaffected. Built-in platform templates can't be deleted.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_templates.delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_templates_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one funnel or website template with its theme, niche, tags, setup checklist, and the full editable document of every page it carries. Use funnel_templates.use to copy all its pages as a private draft, then funnel_pages.ai_edit and funnel_pages.save_content to customize them. This read creates and publishes nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_templates.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_templates_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List the funnel and website templates available to start from: the organization's own saved ones plus the built-in niche library. Returns each template's niche, tags, page names and paths, and setup checklist so you can choose a complete starting point. Every template is a frozen, fully editable copy of its theme and pages; listing creates and publishes nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_templates.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnel_templates_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Freeze a funnel's theme and every page's WORKING DRAFT into a reusable template. It is a snapshot, not a link — editing the funnel afterwards never changes the template, and funnels built from it are never coupled back to it.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_templates.save_from_funnel \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool funnel_templates_save_from_funnel at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a new funnel or website from a template — theme and every page copied in, with fresh component ids. Optionally pass color_scheme to change colors across every page while keeping fonts and layout. Returns each new page id and builder link, plus a setup checklist. Every section remains editable in the builder and by AI: call funnel_pages.ai_edit with a page id, then funnel_pages.save_content to keep the returned document. Everything lands as a DRAFT and is never published automatically; installation sends no messages and charges no payments.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnel_templates.use \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnel_templates_use at https://app.chirply.io/api/mcp, same bearer token, same input.

Per-arm results for an A/B test: visitors, views, form submissions, paid orders, revenue (cents), conversion rate, and a plain-language statistical readout. Conversions = submissions + orders. A verdict is only called "confident" at p < 0.05 with at least 100 visitors in each arm; below that the readout says to keep collecting.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.ab_test_results \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_ab_test_results at https://app.chirply.io/api/mcp, same bearer token, same input.

Accept a one-click upsell or downsell on a funnel — the button on the offer page after a purchase. THIS CHARGES MONEY IMMEDIATELY AND WITH NO CARD ENTRY: it creates a NEW Stripe PaymentIntent and confirms it off-session against the card already saved on the original order, so the buyer is charged again the moment this returns. The only credential involved is the order token, which is why the window is short — the original order must be PAID and less than two hours old, or the charge is refused. What is sold and what it costs come from the upsell block's OWN published definition and the product table, never from this call, so a token buys that page's offer at that page's price and nothing else. Charging the same offer twice on the same order is prevented by a unique constraint, so a repeat call is a no-op rather than a double charge. On success it records the revenue against the page and fires the account's `upsell_accepted` automations, which can send real messages billed to the tenant's own provider accounts. There is no undo — reversing it means refunding in Stripe.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.accept_upsell \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "example",
    "page_path": "example",
    "block_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "token": "example"
  }'

Over MCP the same operation is the tool funnels_accept_upsell at https://app.chirply.io/api/mcp, same bearer token, same input.

Start a REAL purchase through a published funnel's order form: creates the order, creates or matches a Stripe customer on the seller's own account, and returns a PaymentIntent client secret for collecting the card. THIS IS THE LIVE CHECKOUT — unless the funnel is set to test mode (funnels.set_payment_route), the card charged is charged for real, on the tenant's own Stripe, and Stripe's fees apply. What is being sold and what it costs come from the ORDER FORM'S OWN published definition and from the product table, never from this call: you name the block, and the price is re-derived server-side, so there is no way to buy a $997 offer for $1. Nothing is collected yet at this point — the order is created as 'pending' and the card still has to be confirmed by whoever holds the client secret; call funnels.complete_checkout with the returned token once it clears. The returned `token` is a BEARER CREDENTIAL: for the next two hours it alone authorises funnels.accept_upsell to charge the saved card again with no further card entry, so treat it like a password and never store it where a reader of orders could reach it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.checkout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "example",
    "block_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "buyer_email": "ada@example.com"
  }'

Over MCP the same operation is the tool funnels_checkout at https://app.chirply.io/api/mcp, same bearer token, same input.

Settle a funnel order once its card payment has cleared: asks STRIPE whether the payment actually succeeded — the caller's word is never taken for it — and, if it did, marks the order paid, saves the card for one-click upsells, links or creates the buyer's CRM contact, records the revenue against the page, and fires the account's `purchase_made` automations, which can send real email, SMS or voicemail billed to the tenant's own provider accounts. Idempotent: an order already settled (by this call or by Stripe's webhook, which is authoritative and will settle it either way) simply reports 'paid' and does nothing again. This exists because the very next funnel step is usually a one-click upsell, which needs the order to be paid with a saved card NOW rather than whenever the webhook lands. It does not charge anything itself.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.complete_checkout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "token": "example"
  }'

Over MCP the same operation is the tool funnels_complete_checkout at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a draft funnel, standalone website, or members-only member site and seed its home page with a ready-made layout. A member site (kind 'course', kept for compatibility) enables member login but does not publish or grant anyone access. Nothing is visible until funnels.publish is called. Actual courses (modules/lessons/quizzes) are built with the courses.* capabilities and mounted on a member site.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example"
  }'

Over MCP the same operation is the tool funnels_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Create an A/B test on a funnel page: a full, independently editable copy of the page's current live content ("version B"). Created as a DRAFT — no visitor sees it and nothing changes on the live page until funnels.start_ab_test is called. A page can hold one active test at a time; creating a second returns an error naming the existing one.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.create_ab_variant \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_create_ab_variant at https://app.chirply.io/api/mcp, same bearer token, same input.

CONCLUDE AN A/B TEST, IRREVERSIBLY CHANGING WHAT VISITORS SEE. Declaring 'b' OVERWRITES the live page's published content (and its draft) with the challenger's document — every visitor sees it immediately; the beaten version is kept only as a restore point in the page's version history. Declaring 'a' keeps the page exactly as it is and archives the challenger. Either way the traffic split stops and the test cannot be restarted.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.declare_ab_winner \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "winner": "a"
  }'

Over MCP the same operation is the tool funnels_declare_ab_winner at https://app.chirply.io/api/mcp, same bearer token, same input.

PERMANENTLY DESTROY a funnel and everything under it: every page and its published content, every saved version, the funnel's captured submissions, and its connected custom domains. This cannot be undone. Templates already saved from it, and funnels built from those templates, are unaffected.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Archive a draft or paused A/B test without adopting it: the challenger document stops being served or editable, its collected results are closed out, and the test cannot be restarted. The LIVE PAGE IS NOT TOUCHED — visitors keep seeing it exactly as published. A running test must be paused (funnels.stop_ab_test) or concluded (funnels.declare_ab_winner) instead.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.discard_ab_test \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_discard_ab_test at https://app.chirply.io/api/mcp, same bearer token, same input.

Copy a funnel — its theme and every page's working draft — into a brand-new DRAFT funnel on a fresh URL. Component ids are regenerated so the copy and the original can never interfere. Nothing is published, and the original is untouched.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.duplicate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_duplicate at https://app.chirply.io/api/mcp, same bearer token, same input.

Start a durable AI site build that plans, writes and checks native editable pages in the background. Returns a build id immediately; use site_builds.get for progress, issues and the saved draft. Nothing is published. SPENDS REAL MONEY on the account’s connected AI provider, up to max_calls model attempts. The run pauses on missing input or its call limit and can resume without rebuilding completed pages.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.generate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "example"
  }'

Over MCP the same operation is the tool funnels_generate at https://app.chirply.io/api/mcp, same bearer token, same input.

Generate an image from a description, store it in the organization's media bucket, and return its permanent URL for use in a page component's image prop. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.generate_image \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "example"
  }'

Over MCP the same operation is the tool funnels_generate_image at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one funnel with its steps (pages), connected custom domains, theme, and total form submissions. Page documents are omitted — use funnel_pages.get for a page's content.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one FUNNEL checkout order with its buyer, payment status, amount and refunded amount, plus every line item — the main product, any order bump, and each upsell or downsell that was accepted, with what each was charged. commerce.get_order refuses anything that is not a storefront order, so this is the only reader for these. Amounts are in the smallest currency unit (cents). Read-only. The order token is never returned: it is a bearer credential that can charge the card saved on this order.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.get_order \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_get_order at https://app.chirply.io/api/mcp, same bearer token, same input.

Creates an unpublished, editable page from a captured browser page in an account-owned funnel. Source scripts are excluded; no page is published or messages sent.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.import_capture \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "source": {
      "url": "https://example.com",
      "title": "Example",
      "blocks": [
        {
          "kind": "heading",
          "text": "example"
        }
      ]
    }
  }'

Over MCP the same operation is the tool funnels_import_capture at https://app.chirply.io/api/mcp, same bearer token, same input.

Uses the account's Firecrawl connection to read one public URL and create an unpublished, editable page in an account-owned funnel. Firecrawl credits may be billed to the connected provider account. Source scripts are detected and excluded; no page is published.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.import_url \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "url": "https://example.com"
  }'

Over MCP the same operation is the tool funnels_import_url at https://app.chirply.io/api/mcp, same bearer token, same input.

List the organization's funnels, most recently edited first. Each funnel is a sequence of landing pages served at /f/<slug>.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnels_list at https://app.chirply.io/api/mcp, same bearer token, same input.

List the A/B tests in this account — per test: the page it runs on, label, traffic weight, lifecycle status (draft/running/paused/winner/archived), and when it started or concluded. Filter by funnel, page, or status. Use funnels.ab_test_results for the numbers.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list_ab_tests \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnels_list_ab_tests at https://app.chirply.io/api/mcp, same bearer token, same input.

List orders taken through the organization's FUNNEL checkouts — the Orders screen under Funnels — newest first, each with buyer, payment status, amount, refunded amount and, unless you turn them off, its line items (main product, order bump, upsells and downsells). This is the funnel side of the business and it has no other reader: commerce.list_orders answers only for the storefront and hard-excludes everything here. Amounts are in the smallest currency unit (cents), and collected revenue is total minus refunded counting ONLY orders whose status is 'paid' — a 'pending' order is an abandoned checkout, not a sale. Read-only. The order token is never returned: it is a bearer credential that can charge a buyer's saved card.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list_orders \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnels_list_orders at https://app.chirply.io/api/mcp, same bearer token, same input.

List the last 50 immutable public releases for this site, including publications and rollbacks. This reads history without changing drafts or what visitors see.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list_releases \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_list_releases at https://app.chirply.io/api/mcp, same bearer token, same input.

Read website inquiries and funnel opt-in submissions, newest first, including every submitted answer and the linked CRM contact. Filter by website, page or contact. This is read-only; it does not contact anyone or run automations.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list_submissions \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool funnels_list_submissions at https://app.chirply.io/api/mcp, same bearer token, same input.

List complete design themes and color-only schemes for websites and funnels. The presets array includes typography and spacing; color_schemes changes only colors and preserves the design. Pass a color_schemes id as color_scheme.preset to funnels.set_theme or funnel_templates.use. This read saves or publishes nothing.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.list_theme_presets \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool funnels_list_theme_presets at https://app.chirply.io/api/mcp, same bearer token, same input.

Analyze a reference website screenshot and restyle a supplied page document to match its visual direction using only structured, editable builder components. Returns the revised draft document but does not save or publish it — pass it to funnel_pages.save_content to keep it. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good. TWO billed calls per run: the vision pass over the screenshot, then the page edit.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.match_screenshot \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "document": null,
    "image_url": "https://example.com"
  }'

Over MCP the same operation is the tool funnels_match_screenshot at https://app.chirply.io/api/mcp, same bearer token, same input.

PUT THIS FUNNEL ON THE PUBLIC INTERNET. Every validated draft page and the draft theme are published together and become reachable at /f/<slug> (and on any active custom domain) to anyone with the link, with no login. Publish only when the content is ready to be seen by customers.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.publish \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_publish at https://app.chirply.io/api/mcp, same bearer token, same input.

Restore a previously published site's page content, routes, SEO, access presentation and design tokens together for real visitors. Keeps current working drafts and saves the outgoing live state. Running A/B tests are paused. This changes the live site immediately; it does not grant entitlements, change current product prices or charge anyone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.restore_release \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "release_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "expected_revision": "example"
  }'

Over MCP the same operation is the tool funnels_restore_release at https://app.chirply.io/api/mcp, same bearer token, same input.

Rewrite one snippet of page copy — a headline, a subhead, a button label — and return the new text. No page is changed; write the result back with funnel_pages.save_content yourself. SPENDS REAL MONEY: it runs on the organization's OWN OpenRouter API key, so the model charge lands directly on the tenant's OpenRouter bill. There is no credit pool and no free allowance — every call is billed and metered against this account, whether or not the result is any good.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.rewrite_copy \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "example",
    "instruction": "example"
  }'

Over MCP the same operation is the tool funnels_rewrite_copy at https://app.chirply.io/api/mcp, same bearer token, same input.

Choose which connected Stripe account collects the money for a funnel, and whether it charges in live or test mode. THIS DECIDES WHERE REAL CUSTOMER MONEY LANDS. Pointing it at the wrong account sends this funnel's takings to another business's Stripe; setting mode to 'test' means every checkout on the funnel's LIVE published pages silently stops charging anyone — the pages keep working and buyers keep getting confirmation, and nothing is collected. It applies from the next checkout onward: orders already placed keep the account and mode pinned onto them at the time, so nothing in the past moves. The equivalent for a storefront is commerce.update_store; funnels.update deliberately does not accept these two columns, so this is the only way to set them.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.set_payment_route \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "stripe_account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_set_payment_route at https://app.chirply.io/api/mcp, same bearer token, same input.

Save site-wide design tokens as an unpublished draft. To change only colors and preserve fonts, spacing, buttons and content, pass color_scheme with a preset or custom brand/background colors. Alternatively pass a complete theme preset, overrides, or both. Every page uses the changes after the next publish; no live page changes or messages are sent now.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.set_theme \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_set_theme at https://app.chirply.io/api/mcp, same bearer token, same input.

PUT THE TEST IN FRONT OF REAL VISITORS. From the moment this runs (within about a minute of cache), the chosen percentage of visitors to the page is served the challenger document instead of the live page. Assignment is deterministic and sticky per visitor. Also resumes a paused test. The variant must not have concluded.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.start_ab_test \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_start_ab_test at https://app.chirply.io/api/mcp, same bearer token, same input.

Conversion stats per step for a funnel over the last N days: views, unique visitors, form submissions, paid orders and revenue (cents, net of refunds). This is what the Performance report on the funnel page shows.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.stats \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_stats at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause a running A/B test: within about a minute every visitor sees the original page again. Results collected so far are kept, and the test can be resumed with funnels.start_ab_test or concluded with funnels.declare_ab_winner.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.stop_ab_test \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_stop_ab_test at https://app.chirply.io/api/mcp, same bearer token, same input.

Submit a real opt-in form on a PUBLISHED funnel page, exactly as a visitor filling it in would. THIS IS NOT A TEST: it creates or updates a REAL CRM CONTACT from the email and phone in the answers, stores a funnel submission against the page, counts toward that page's conversion stats, and immediately fires every `form_submitted` automation in the account — which can send real email, SMS or ringless voicemail to that person and bill the tenant's own provider accounts for it. There is no draft and no undo. Field names and which are required are read from the form's OWN published definition, not from what you send, so an answer for a field the form does not have is ignored and a missing required field is an error. Deduplication is the platform's: one phone number is one contact, matched on email first and then phone in any spelling it might be stored under, so submitting twice updates one person rather than creating two. Use funnels.list_submissions to read what has already come in.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.submit_form \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "example",
    "block_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "values": {}
  }'

Over MCP the same operation is the tool funnels_submit_form at https://app.chirply.io/api/mcp, same bearer token, same input.

Take a live funnel off the public internet. Visitors on /f/<slug> and on any custom domain immediately stop being able to reach it. Content and pages are kept — publish again to restore it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.unpublish \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_unpublish at https://app.chirply.io/api/mcp, same bearer token, same input.

Rename a funnel or change its description or public slug. CHANGING THE SLUG MOVES THE FUNNEL'S PUBLIC URL: every link already shared at the old /f/<slug> — in sent emails, in live ads, on printed material, in other people's posts — breaks immediately and there is no redirect from the old address. Renaming alone is internal and safe; the slug is the irreversible part. Omitted fields are left alone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Change an A/B test's challenger: its document (same Puck shape as a page's content), its label, or the share of traffic that sees it. Pause a running test before editing it. Concluded tests cannot be edited.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/funnels.update_ab_variant \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "variant_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool funnels_update_ab_variant at https://app.chirply.io/api/mcp, same bearer token, same input.

Add a new draft page to an existing funnel or website from an individual-page template. Complete multi-page website templates must use funnel_templates.use so no pages are discarded. The copied builder document receives fresh component ids, stays fully editable, and is never published automatically.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/page_templates.add_to_funnel \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "funnel_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "template_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool page_templates_add_to_funnel at https://app.chirply.io/api/mcp, same bearer token, same input.

Freeze one funnel page's current working draft as a reusable individual-page template. It is a private snapshot; later edits to either the source page or a copied page never change the other.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/page_templates.save_from_page \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool page_templates_save_from_page at https://app.chirply.io/api/mcp, same bearer token, same input.

Take a product out of the builder's pickers (archive) or put it back (restore). Products are archived rather than deleted because past orders reference them and a sold product has to stay resolvable for reporting.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/products.archive \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool products_archive at https://app.chirply.io/api/mcp, same bearer token, same input.

Add a sellable product to the catalogue so it can be attached to an order form, an order bump or a one-click upsell inside the builder. Creating a product charges nobody — checkouts run on the organization's own connected Stripe account, and nothing can be sold until Stripe is connected.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/products.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example",
    "price": "example"
  }'

Over MCP the same operation is the tool products_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one product with its pricing, currency and billing interval.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/products.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool products_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List what the organization's funnels sell. A product can be the main offer on one funnel's order form and the order bump or one-click upsell on another. Amounts are integer cents.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/products.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool products_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Update a product's name, price, currency, billing kind, artwork, or which Stripe account and live/test mode it charges on. THIS CHANGES WHAT REAL BUYERS ARE CHARGED: a new price takes effect at the next checkout on every funnel offering this product, and switching payment_mode to 'test' means live customers' cards stop actually being charged while the pages carry on looking like they are working (switching to 'live' does the reverse). Past orders are never rewritten — an order item copies the amount at purchase time. Omitted fields are left alone.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/products.update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool products_update at https://app.chirply.io/api/mcp, same bearer token, same input.

Append a fresh editable copy of a saved section to the bottom of a page's working draft. The public page is unchanged until someone publishes it.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/section_templates.insert_into_page \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "template_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool section_templates_insert_into_page at https://app.chirply.io/api/mcp, same bearer token, same input.

Freeze one top-level section from a page's working draft as a reusable section template, including its nested columns, copy, images, and styles. Creating the template publishes nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/section_templates.save_from_page \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "page_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "component_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool section_templates_save_from_page at https://app.chirply.io/api/mcp, same bearer token, same input.

Approve the exact reviewed CMS draft entries, local membership access definitions and paused manual follow-up workflows for a site build. CMS and access setup requires account management permission. Reviewed access setup enables native login for an unpublished new site; an existing published site requires explicitly enabling login first. Creates no member grants, sends no messages, activates no workflow and publishes no pages. Continuing the build SPENDS REAL MONEY within its already approved AI allowance.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.approve_resources \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "expected_revision": "example",
    "resources": {}
  }'

Over MCP the same operation is the tool site_builds_approve_resources at https://app.chirply.io/api/mcp, same bearer token, same input.

Cancel the remaining AI work for a site build. Completed draft pages and activity stay available. No more tasks can commit results; provider requests already sent may still be billed. Cancelling does not unpublish or delete any site.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.cancel \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool site_builds_cancel at https://app.chirply.io/api/mcp, same bearer token, same input.

Read a saved site's build plan, task progress, issues and activity. Reports partial and failed work explicitly. This polling call never spends money or drives the runner.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool site_builds_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List up to 200 active products and booking events in this account for resolving a site's build plan. Returns resource ids and names only; makes no paid calls and changes no records.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.input_resources \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool site_builds_input_resources at https://app.chirply.io/api/mcp, same bearer token, same input.

List saved AI site builds in this account, including progress, remaining call allowance and unresolved issues. Reads only; it does not run a model or change any page.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25
  }'

Over MCP the same operation is the tool site_builds_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause an AI site build at its saved checkpoint. A provider request already sent may still be billed, but its late result cannot overwrite the draft after this control takes effect. Completed draft pages are kept.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.pause \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool site_builds_pause at https://app.chirply.io/api/mcp, same bearer token, same input.

Retrieve authoritative provider receipts for uncertain requests already sent by this build, updating actual charges and releasing only reconciled reservations. Makes no new AI generation request and incurs no generation charge. Missing provider receipts remain explicitly uncertain.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.reconcile_spend \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool site_builds_reconcile_spend at https://app.chirply.io/api/mcp, same bearer token, same input.

Resume an AI site build from saved progress, retrying unfinished work. SPENDS REAL MONEY on the account's connected AI provider within the remaining call allowance. Optionally authorize additional paid attempts; completed pages are preserved and nothing is published.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.resume \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool site_builds_resume at https://app.chirply.io/api/mcp, same bearer token, same input.

Apply a reviewed sitemap revision and continue building added or explicitly selected pages. Preserves existing page content by default and keeps excluded pages intact. Changes draft routes and shared navigation; nothing is published. Resumed generation SPENDS REAL MONEY within the existing AI call and dollar allowances.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.revise_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "expected_plan_revision": 1,
    "plan": null
  }'

Over MCP the same operation is the tool site_builds_revise_plan at https://app.chirply.io/api/mcp, same bearer token, same input.

Change the total authorized AI provider spending limit for a saved build. This authorizes REAL MONEY spending when the build resumes. Explicit null removes the dollar cap while retaining its AI call allowance. The new cap must cover recorded charges and outstanding reservations. Pause active work before changing it; this action does not resume the build.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/site_builds.set_budget \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "expected_revision": "example",
    "max_spend_usd": 1
  }'

Over MCP the same operation is the tool site_builds_set_budget at https://app.chirply.io/api/mcp, same bearer token, same input.