Usage-Based Pricing and Agency Rebilling on the Sparkforge App Marketplace

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge App Marketplace supports usage-based pricing in three modules — per-execution, per-message, and custom event. Agencies add markups, set daily caps, and bill the right wallet.

The Sparkforge App Marketplace supports usage-based pricing so developers can charge per execution, per message, or per custom event. Agencies add markup, set daily caps, and pick which wallet absorbs the charge.

What it is

Usage-based pricing ties charges to actual app activity instead of a flat subscription. Agency rebilling lets you resell those charges with your own markup and bill clients through their sub-account wallet.

Three pricing modules are supported: per-execution fees on Actions and Triggers, per-message fees on Conversation Providers (separate inbound and outbound rates), and custom per-usage fees on app-defined events posted via the Marketplace billing APIs.

Why it matters

Aligned costs: Charges track real activity, not flat plans.
Granular control: Pick per-execution, per-message, or custom events.
Agency margin: Markup controls add profit on top of developer pricing.
Spend protection: Daily caps prevent bill shock.
Billing clarity: Clear rules for which wallet gets charged.

Pricing modules

Per-execution (Actions and Triggers)

Charge each time an action or trigger runs. Useful for workflow-heavy or automation-driven apps.

Unit: One execution of a supported action or trigger.
Typical use: Premium actions, data enrichment, sync steps.
Configure: App → Pricing → enable Actions and Triggers, set the per-execution price.

Per-message (Conversation Providers)

Messaging cost varies by direction. Inbound and outbound rates are set separately.

Unit: One message handled by the Conversation Provider.
Directional pricing: Distinct Inbound and Outbound prices.
Configure: App → Pricing → Conversation Provider pricing fields.

Custom per-usage (app-specific events)

Bill for unique events like minutes, tokens, or scanned items. Define your own event and post usage via the billing APIs.

Examples: Per minute of AI voice, per token, per scanned item.
Configure: App → Pricing → Custom Event (API-billed). Define price per unit; post usage via billing APIs.
Validate: Post test usage and confirm charges before go-live.

Billing controls

Control	What it does	Where to configure	Effect
Agency Markup	Adds margin to per-use pricing	App Marketplace → App Reselling	Raises per-unit price billed to client when rebilling is on
Rebilling ON	Bills the client's sub-account wallet	Agency billing settings	Usage debits sub-account wallet
Rebilling OFF	Bills the agency wallet	Agency billing settings	Usage debits agency wallet
Daily Usage Limits	Caps daily billable units per app	App Marketplace → Usage Limits	Usage pauses at cap; resumes next day

Set up reselling and rebilling

Open App Marketplace, pick the app, then App Reselling (Usage-Based).
Click Set Usage-Based Pricing, enter your markup, save.
Open App Marketplace → Usage Limits and set daily caps. Save.
Confirm Rebilling is on so charges hit the sub-account wallet.

Where to view charges

App pricing details show on the app's Details page under the Pricing section. For Workflow Actions and Triggers, usage pricing also appears in the Workflow Builder's Discover tab.

Frequently Asked Questions

Who is billed when rebilling is on versus off?

With rebilling on, the sub-account wallet is charged. With rebilling off, the agency wallet is charged.

Can I set different inbound and outbound message prices?

Yes. Conversation Providers support distinct inbound and outbound per-message rates. Configure them separately in the app's pricing fields.

Are markups per app or per client?

Per app. Markup is configured at the app level for usage-based apps. Clients only see the agency price, not the underlying developer rate.

What happens when a daily limit is reached?

Billable usage for that app pauses for the rest of the day and resumes after the daily reset. Set caps to match your client's budget and expected volume.

Can I combine subscription and usage pricing?

Yes, when the app supports it. Use a subscription for access and usage-based pricing for consumption charged on top.