Reseller

List every scheduled client report this agency has configured: which client, weekly or monthly, the recipient emails, whether it's enabled, when it last sent, and any delivery error. Read-only.

Parameters

No parameters — POST an empty body.

Example

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

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

Build a branded client report for the latest completed UTC week or month, returning subject, numbers, fetch time, and HTML without sending email. Unavailable source sections are null and visibly labeled; incomplete reports cannot be sent.

Parameters

Example

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

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

Read each active client's new contacts, calls, connect rate, messages, appointments, reviews, and collected net revenue for a UTC period. Failed sources return null metrics and unavailable section names, never zero. Revenue totals disclose client coverage. Read-only; sends no messages.

Parameters

Example

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

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

Assemble and email a client's branded performance report for the latest completed UTC week or month — a REAL email through the agency's connected Mailgun/Resend account, billed to the agency. Delivery is held if any source section is unavailable. Use preview to inspect without sending.

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/client_reports.send_now \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Create or update the standing report for one client account: weekly or monthly cadence, the client emails it goes to, and whether it's on. Enabling it means a real branded report email is sent to those addresses automatically after each period ends, through this agency's own connected email account. No email is sent by this call itself.

Parameters

Example

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

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

Manually add or remove credits from a client's balance (a comp, a correction). A positive amount grants credits; a negative amount deducts them. Adding credits lifts a paused client back into service. This changes a real balance the reseller is liable for, so it's confirm-gated.

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/reseller.adjust_client_credits \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "amount_dollars": 1
  }'

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

Set a client account to one of the ready-made shapes — the full platform, CRM only, marketing suite, phone and voice, or inbox only. This REPLACES the client's whole switchboard: every section the preset does not keep is hidden, including features added to Chirply after the preset was written. Use reseller.get_client_features to see what each preset keeps before applying one. Reversible — apply 'everything' to restore the full platform. Does not change their plan or their bill.

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/reseller.apply_client_feature_preset \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "preset_id": "everything"
  }'

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

Retire a plan so it can no longer be assigned or sold. Clients already on it keep it and keep working — nothing is deleted and nobody's billing changes — but the plan disappears from the pickers. There is no un-retire; recreate it if needed.

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/reseller.archive_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Assign an agency-owned domain to this client account. Once active, visitors sign in to the assigned account with the agency's branding. Changes live application routing, costs nothing, and preserves domain ownership. Requires White-Label; a domain assigned to another client must be unassigned first.

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/reseller.assign_client_domain \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Put a client account on one of the agency's plans, or clear it. This changes what a paying third-party business can actually do straight away, because the plan pins their underlying platform tier and limits — moving them down a tier removes features and can push them over a limit they are currently using. It does NOT charge them or change an existing subscription — billing is started separately with reseller.start_client_billing — so the money and the entitlements can end up out of step until someone reconciles 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/reseller.assign_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Cancel a client's subscription on the agency's Stripe. By default it ends when the period they've already paid for runs out; `immediately` cuts it off now, which forfeits the rest of a period they have already been charged for and is not reversible. Does not suspend or delete their account.

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/reseller.cancel_client_billing \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Move the current CLIENT account to another of its agency's plans. Changes the customer's subscription on the AGENCY's connected Stripe account (never the platform's) and switches the account's features to the new plan immediately. During a free trial nothing is charged: the trial keeps its end date and the new plan's price is charged when it ends. Outside a trial the new price applies at once — Stripe credits the unused part of the current plan and adds the difference to the next invoice, or, when the billing interval changes (monthly to yearly or back), starts a new billing period and charges the card on file today. A declined charge leaves the plan unchanged. Only for client accounts that signed up through the agency's store; a plan the agency bills or sets directly is changed by the agency (reseller.assign_plan). Check reseller.client_plan first for the plans on offer.

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/reseller.change_client_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Read this agency's store checkout requirements: whether buyers must tick a confirmation box (and its exact text and current version), whether the order form collects a company name and VAT ID, the legal links shown on every store page, whether Stripe Tax is on (and the latest reason Stripe refused tax, if any). Also returns the store's checkout address and the exact form field names, with which are required, for an agency's own website that posts orders directly. Changes nothing.

Parameters

No parameters — POST an empty body.

Example

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

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

Read the current CLIENT account's plan the way its agency sells it: the plan's name, price and billing interval, the subscription status, trial end and renewal date, the agency's other plans this account can switch to, and whether switching is self-serve here (only for accounts that signed up through the agency's store). Only works inside a client account — one created under an agency. Read-only; nothing is charged.

Parameters

No parameters — POST an empty body.

Example

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

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

Read the subscription status and period end for the current client account's reseller subscription. Requires an account owner or admin. Does not change billing or access.

Parameters

No parameters — POST an empty body.

Example

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

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

Verify a confirmed SetupIntent with the reseller's Stripe and record the resulting payment method as the client's saved card for credit top-ups and auto-recharge. Refuses unless Stripe itself reports the setup succeeded for this client's customer. Moves no money.

Parameters

Example

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

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

Connect a hostname the agency already owns and assign it to this client account. Requests a public HTTPS certificate, consumes an agency domain slot, and changes where the app opens once DNS is verified. Does not buy a domain or edit DNS; the owner adds the returned CNAME at their provider. Requires White-Label. Existing published content and assignments to other clients are protected.

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/reseller.connect_client_domain \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain": "example"
  }'

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

Create a new client account under this agency, optionally putting it straight onto one of the agency's plans. Counts against the agency's paid client account allowance and fails once that's used up. The account starts empty with nobody in it — invite the client with reseller.invite_client_user. Assigning a plan here pins their tier and limits immediately but charges nobody; billing is started separately.

Parameters

Example

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

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

Create a plan this agency sells to its clients: a name the client sees on their invoice, the price the agency charges, which underlying platform tier it unlocks, optional per-limit tweaks on top of that tier, and optionally its own free-trial length on the agency's launch store (trial_days; default: the store's trial). Creating a plan costs nothing and charges nobody — it only defines a package. Clients are put on it separately with reseller.assign_plan.

Parameters

Example

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

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

Create a hosted Stripe checkout link for one published reseller plan on this agency's connected Stripe account. Completing checkout charges the chosen price or starts its configured trial, creates a client account, and enables approved customer emails. This call creates the link only and does not submit a payment or enroll the recipient into marketing nurture. A link created here goes straight to payment, so the store's confirmation checkbox is not shown and no confirmation is recorded for it. While the store's 'Every signup starts with the free trial' setting is on, the link always includes the trial. The trial length is the plan's own when it sets one (reseller.update_plan trial_days), otherwise the store's; a plan set to 0 days is always charged at checkout, trial or not.

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/reseller.create_signup_checkout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Delete a client account. This is a soft delete: the account is closed and everyone in it is locked out immediately, but nothing is destroyed — it can be restored later with reseller.restore_client. It stops counting against your paid client account allowance, so deleting a client frees a slot to create another. It does NOT cancel any billing you have running for them on your Stripe — stop that separately with reseller.cancel_client_billing.

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/reseller.delete_client \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Turn off a pooled provider for a client. By default this is a reversible soft off — the client goes back to using its own connection and the isolation artifacts are kept, so re-enabling is instant. Set teardown to also SUSPEND the Twilio subaccount (reversible, keeps the client's numbers) or DELETE the Mailgun subdomain.

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/reseller.disable_pooled_credential \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "provider": "twilio"
  }'

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

Turn off Stripe Connect for a client. Reversible: the client goes back to selling on its own Stripe, and the connected account is kept so you can switch it back on instantly. Does not move or refund any money already collected.

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/reseller.disable_stripe_connect \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Let a client account use YOUR provider account instead of connecting its own. For Twilio this creates an isolated Twilio subaccount under your master account — the client's calls and texts run on it and Twilio bills YOU for them. For Mailgun it provisions an isolated sending subdomain (which needs its DNS verified before it goes live). For ElevenLabs / OpenRouter / Outscraper / Firecrawl it uses your API key directly, effective immediately. The client's usage becomes your real cost — meter and rebill it with the credit system. Reversible at any time.

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/reseller.enable_pooled_credential \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "provider": "twilio"
  }'

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

Turn on Stripe Connect for a client: create (or reuse) an Express connected account under YOUR Stripe platform so the client can accept card payments through you. Money settles to the client and they stay merchant of record; you take an application fee on each transaction (set separately). This does NOT finish setup — the client must still complete Stripe's identity + bank verification (a link, from get_stripe_connect_link) before they can accept a payment. Requires your own Stripe to be connected and have Connect enabled. Reversible.

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/reseller.enable_stripe_connect \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Whether this agency has connected its own Stripe account, which is required before it can charge any client. Read-only.

Parameters

No parameters — POST an empty body.

Example

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

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

Everything about one client account: its plan, the people in it, outstanding invitations, and its billing state on the agency's own Stripe. Read-only.

Parameters

Example

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

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

A client's prepaid credit standing on the reseller's pooled providers: balance (cycle allowance + purchased), whether it's paused for being out of credits, its effective per-unit prices, and its recent credit ledger. Read-only.

Parameters

Example

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

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

For one client account, list every feature you can switch on or off for them and which ones are currently hidden. Returns the full catalog — sections (Sites, Phone, AI…) and the individual rows inside each — plus the one-click presets. Hidden features are gone from that client's navigation, their pages don't open, and their API keys and integrations can't reach them, with no upgrade prompt shown anywhere. This is separate from the client's plan and does not change it. Read-only.

Parameters

Example

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

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

Read the per-item prices a reseller charges. With a client_id, returns that client's effective prices (override → plan default → agency default) plus its own overrides. Otherwise returns the default prices for a plan (or the agency-wide default when no plan_id is given). Each price also reports `markup_percent`: the percentage on cost it was written as, or null when it is a fixed dollar amount. Read-only, costs the caller nothing.

Parameters

Example

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

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

For one client account, show whether it accepts payments through YOUR Stripe (a connected account under your platform) or its own. Reports the status (own Stripe / onboarding / restricted / live), whether charges and payouts are enabled, and the application fee you take on its transactions (the per-client override or the plan default). Read-only.

Parameters

Example

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

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

Mint a fresh Stripe onboarding link for a client's connected account — the URL the client opens to complete identity + bank verification. The link is single-use and expires within minutes, so generate it when you're about to send it. Connect must already be enabled for the client.

Parameters

Example

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

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

Read what each metered unit costs the RESELLER at their own provider — the base every percentage mark-up price is worked out from. Units the reseller has not given a figure for report Chirply's published list price for that provider, flagged with is_custom false. This is the agency's margin data and is never visible to a client. Read-only.

Parameters

No parameters — POST an empty body.

Example

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

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

Invite someone into a client's account — normally the client themselves, so they can log in and use the platform. Creates a pending invitation they accept to join; it grants them access to that one account only, never to the agency. Sends a real invitation to a real email address.

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/reseller.invite_client_user \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "email": "ada@example.com"
  }'

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

Read the current reseller website, offer terms (including trialOnly: whether every signup starts with the free trial and the paid signup page opens the trial signup; planTrials: each live plan's free trial as the store sells it — its own trialDays when set, null when it follows the store, and sellsWithTrialDays; trialOnlyExceptions: plans sold without a trial while trial-only is on), marketingOptIn (whether a ticked 'Email me setup tips' box is confirmed by double opt-in before setup tips start — state confirming, off, not_started or channel_off — how many buyers are waiting to confirm, and the Email preferences link that changes it), connection readiness, public funnel links, and recent signup failures for this agency. Does not publish or send messages.

Parameters

No parameters — POST an empty body.

Example

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

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

List agency-owned domains, their DNS and HTTPS status, and assigned client account IDs. Read-only; changes no routing and costs nothing. An app_org_id matching the client is its dedicated account address; null means unassigned.

Parameters

Example

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

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

List who can sign in to a client account, plus any invitations that haven't been accepted yet. Read-only.

Parameters

Example

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

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

List every client account (client account) under this agency, with the included client-account allowance, used and remaining capacity, the plan each one is on, how many people are in it, and whether the agency is billing them. Includes soft-deleted clients — those have status 'canceled' and can be brought back with reseller.restore_client. Read-only.

Parameters

No parameters — POST an empty body.

Example

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

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

The sending domains on YOUR OWN connected Mailgun account, with whether each one is verified. Use it to choose which domain a pooled client should send from. Sandbox domains are left out on purpose: Mailgun only lets those reach addresses you have individually authorised, so a client placed on one would appear to be sending while reaching almost nobody. Reads only.

Parameters

No parameters — POST an empty body.

Example

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

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

List the plans this agency sells to its clients — the reseller's own packages, with the price the reseller charges, which underlying platform tier each one unlocks, and each plan's own free trial on the launch store (trial_days: null = the store's trial, 0 = no trial). These are NOT the platform's own retail plans; they're what this agency resells under its own brand.

Parameters

Example

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

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

For one client account, show which providers it's using YOUR pooled credentials for versus its own. Each row reports the provider, whether pooling is on, its status (off / provisioning / active / error), and any isolation detail (the Twilio subaccount SID, the Mailgun subdomain and its DNS state). Read-only.

Parameters

Example

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

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

Create a secure Stripe portal link for the current client account's own reseller subscription. The customer can update payment details, view invoices, and cancel at period end there. Opening this link does not itself charge or cancel the subscription.

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

No parameters — POST an empty body.

Example

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

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

Close the public reseller offer and pause queued customer lifecycle emails. Existing Stripe subscriptions keep billing and automatic account access checks continue. Does not cancel customer subscriptions or delete data.

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

No parameters — POST an empty body.

Example

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

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

Prepare a draft reseller website, trial and paid signup funnels, and customer lifecycle email templates. Seeds suggested plans only when the agency has not seeded them previously. Does not publish, charge, or email customers.

Parameters

Example

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

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

Publish the reseller website and both signup funnels after connection and test checks pass. Enables real customer invitation, onboarding, trial, payment recovery and cancellation emails through the agency sending provider. Future signups create client accounts and subscriptions billed to the agency connected Stripe account; email and processing fees may apply.

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

No parameters — POST an empty body.

Example

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

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

Re-check a client's connected account with Stripe and update whether it can accept charges and receive payouts. Use after the client finishes onboarding to confirm they're live. Charges nothing.

Parameters

Example

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

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

Remove this client's dedicated account assignment from one agency-owned domain. Immediately restores shared agency sign-in at that hostname. Keeps the domain connection, HTTPS certificate and agency ownership; costs nothing. Requires White-Label.

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/reseller.remove_client_domain \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Rename a client account. Cosmetic — the URL slug and everything inside it are untouched.

Parameters

Example

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

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

Set the order this agency's live plans appear in on its public store — the pricing page, the trial and paid signup funnels — and in every plan picker. List plan ids first to last; any live plan left out keeps its current relative place after the ones named. After this call the agency's own order is kept exactly, and a plan created later joins the end of it. Changes display order only: no price, plan contents, client assignment or billing changes, and nothing is sent to anyone. Use reseller.sort_plans_by_price to return to the automatic lowest-price-first order.

Parameters

Example

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

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

Bring a deleted (cancelled) client account back to active, with all its data intact. Fails if you're already at your paid client account allowance — free a slot or upgrade first, since a restored client counts again.

Parameters

Example

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

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

Withdraw a pending invitation into a client account. Their invite link stops working. Anyone who already accepted is unaffected.

Parameters

Example

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

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

Change the public store's checkout requirements for new orders: require a confirmation checkbox with the given text (links as [text](https://url)), collect a company name and VAT ID (off, optional or required), set the legal links shown on every store page, and turn Stripe Tax on or off. With Stripe Tax on, new checkouts add or include tax calculated by the agency's own Stripe account, and turning it on is refused unless Stripe Tax is active there. Takes effect immediately on the live store and on orders the agency's own website posts to the store checkout; while the checkbox is required, the checkout refuses any order that does not send terms_accepted. Omitted fields keep their saved values. Does not charge, email or change existing subscriptions.

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/reseller.save_checkout_terms \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "terms_required": true,
    "terms_text": "example"
  }'

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

Set the connected Stripe account, website domain, trial duration, payment grace period, and whether every signup starts with the free trial (trial_only: the paid signup page then opens the trial signup and every new checkout includes the trial) for future reseller signups. Changes an already published offer for new customers; existing subscriptions retain their terms. Does not charge or email 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/reseller.save_launch \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "stripe_account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "trial_days": 1,
    "grace_days": 1
  }'

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

Turn this agency's store alerts on or off and choose where they go. When on, the agency is emailed — from its own verified sending address, the same one its store uses — each time a customer starts a trial, places a paid order, converts from trial, switches plans (with the old plan, the new plan and when it takes effect), fails a renewal payment, pays a failed renewal or ends a subscription, and its owners' and admins' browsers get a notification. A blank email sends alerts to the agency's owners and admins (up to five, owners first). Every alert carries the buyer's name, email and company, so the chosen address receives that customer data from now on — confirm it belongs to the agency. Sends nothing by itself and costs nothing beyond the agency's normal email sending.

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/reseller.save_store_alerts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true
  }'

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

Email one sample store alert right now — a made-up 'new trial' for the store's first plan — to whoever currently receives this agency's store alerts, from the agency's own sending address. Lets the agency confirm the alert arrives and where. Sends one real email per recipient (up to five); creates no signup, client account or charge.

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

No parameters — POST an empty body.

Example

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

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

Turn a client's credit auto-recharge on or off and set its rules. While on, whenever a pooled-usage debit drops the client's balance under the threshold, their SAVED card is automatically charged the recharge amount on the RESELLER'S OWN Stripe — unattended, real-money charges, at most one attempt per 15 minutes. Confirm-gated because saving these settings arms future charges nobody clicks on.

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/reseller.set_client_auto_recharge \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true
  }'

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

Replace the whole list of features hidden from one client account. Pass every feature id you want HIDDEN; anything you leave out becomes visible, so sending an empty list restores the full platform. A hidden feature disappears from that client's navigation, its pages stop opening, and the client's own API keys, MCP sessions and Copilot can no longer reach it — no upgrade prompt is shown, because there is nothing for them to buy. Nothing is deleted: their existing data stays and comes back untouched if you switch the feature on again. Does not change their plan or their bill.

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/reseller.set_client_features \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "hidden": [
      "example"
    ]
  }'

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

Suspend a client account so nobody in it can sign in — how an agency handles a client who has stopped paying — or reactivate a suspended one. Nothing is deleted and it is fully reversible, but suspending locks real people out of their account immediately.

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/reseller.set_client_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "active"
  }'

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

Set which Mailgun domain a pooled client sends from, instead of the automatic `<client>.<your root domain>` subdomain. Give a domain already verified on your Mailgun account and the switch takes effect immediately with no DNS to publish. Give a new one and it is created, and the client KEEPS SENDING ON THEIR OWN CONNECTION until its DNS is published and verified — their mail does not stop, but it is not on your account either. THIS CHANGES THE FROM-DOMAIN ON MAIL THEIR CUSTOMERS RECEIVE, which affects how that mail is recognised and filtered, so it is not a cosmetic setting.

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/reseller.set_pooled_mailgun_domain \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "domain": "example"
  }'

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

Set what a reseller charges per metered unit, as a fixed price or as a percentage mark-up on what the unit costs them. With a client_id, sets that client's overrides; with a plan_id, the plan's defaults; with neither, the agency-wide defaults. A mark-up price is recomputed from the cost basis (see reseller.get_unit_costs) every time it is charged, so correcting a cost re-prices every unit priced that way. Setting a price changes what the client is billed for future usage on your pooled credentials — it moves no money by itself and bills nobody retroactively. Unknown units are ignored with a warning.

Parameters

Example

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

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

Set the application fee you take on this client's transactions, in basis points (100 = 1%, max 10000 = 100%). This is money taken off the top of another business's card revenue, and at 10000 it takes all of it — so confirm the number with a human before saving. It is a per-client override; pass null to clear it and inherit the client's plan default instead. Applies to future charges once Connect charge routing is live.

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/reseller.set_stripe_connect_fee \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "fee_bps": 1
  }'

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

Record what metered units actually cost the reseller at their provider, in dollars per unit (e.g. {"sms": 0.0079}). This is agency-wide and is the base for every price written as a percentage mark-up, so changing a cost immediately changes what EVERY client on a mark-up for that unit is charged for future usage — it moves no money by itself and never re-bills past usage. Units listed in `reset` fall back to Chirply's published list price. Unknown units are ignored with a warning.

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/reseller.set_unit_costs \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

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

Read what buyers confirmed when they ordered from this agency's store: the time, the exact confirmation text and its version, the host that sent the order (the store page or the agency's own website), the buyer's network address and browser, and the company name and VAT ID they gave. Signups started from a link the agency created itself are marked created_by: team, with the note: Created by your team — no buyer confirmation recorded. Narrow to one client account or one signup. Returns personal data about the agency's buyers; changes nothing.

Parameters

Example

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

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

Return this agency's plans to the automatic order on its store, signup funnels and plan pickers: monthly plans first, then yearly, each from the lowest price to the highest. Clears any order the agency arranged by hand. Changes display order only — no price, plan contents, client assignment or billing changes, and nothing is sent to anyone.

Parameters

No parameters — POST an empty body.

Example

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

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

SPENDS THE CLIENT'S MONEY. Subscribes a client to one of the agency's plans on the AGENCY'S OWN Stripe account and has Stripe email them an invoice immediately, due in 7 days, recurring at the plan's price and interval. The money goes to the agency; the platform neither holds it nor takes a cut. Requires the agency to have connected Stripe. Fails if the client already has a live subscription.

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/reseller.start_client_billing \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "contact_email": "ada@example.com"
  }'

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

Begin saving a payment card for a client's credit top-ups. Creates (or reuses) a customer on the RESELLER'S OWN Stripe account and returns a SetupIntent client_secret plus the reseller's publishable key, for a Stripe Payment Element the CLIENT completes in a browser. No money moves and no card data passes through this call — the card is entered directly into Stripe's form. Finish with reseller.complete_client_card_setup.

Parameters

Example

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

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

Read whether this agency is emailed about its own reseller store — when a customer starts a trial, places a paid order, converts from trial, switches plans, fails a renewal payment, pays a failed renewal, or ends a subscription — who those emails go to right now (the chosen alert address, or else the agency's owners and admins), and the most recent alerts with their delivery status. Changes nothing.

Parameters

Example

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

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

Re-read a client's subscription from the agency's Stripe account and update the status shown here. This platform receives no webhooks from a tenant's own Stripe, so a payment that failed over there is only noticed when this runs. Read-only as far as Stripe is concerned — it charges nothing.

Parameters

Example

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

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

Create a Stripe test-mode checkout link for an agency plan using its saved trial terms (the plan's own trial length when it sets one, otherwise the store's). Requires test credentials. No real money is charged and no live client or customer email is created. Complete checkout with a Stripe test payment method to verify it.

Parameters

Example

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

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

Immediately charges the client's SAVED card on the RESELLER'S OWN Stripe account for a credit top-up — real money, billed to the client by the reseller — and adds the amount to the client's credit balance once Stripe confirms the charge settled (which also resumes paused pooled sends). Between $5 and $2,000. Refuses when no card is saved (see reseller.start_client_card_setup).

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/reseller.top_up_client_credits \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "amount_dollars": 1
  }'

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

Change a plan's name, price, billing interval, which underlying platform tier it unlocks, its per-limit tweaks, its default Stripe Connect application fee, or its own free trial on the agency's launch store (trial_days: 0 sells it with no trial and charges at checkout, even while the store is trial-only; null follows the store's trial). This edits a package the agency SELLS: every client already on the plan immediately follows its new tier and limits, so lowering a tier or a limit can take a working feature away from a paying customer, and the new price is what the next client to sign up pays. Their existing Stripe subscription is NOT re-priced — changing what a live customer pays has to be done deliberately by cancelling and re-starting their billing. Raising connect_fee_percent raises the cut taken on every client on this plan's live Stripe Connect payment volume immediately, unless that client carries their own fee override.

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/reseller.update_plan \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "plan_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

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

Re-check DNS and HTTPS certificate status for a domain assigned to this client account and save its connection status. Changes only the stored verification state, edits no DNS and costs nothing. Requires White-Label.

Parameters

Example

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

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

Re-check a pooled Mailgun subdomain's DNS with Mailgun and flip it live once the records verify. Only applies to Mailgun; the other providers need no verification. Charges nothing.

Parameters

Example

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

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