Cost per task: a census of 149 listings

Commercially it is prepaid credits bought on an order form and tied to user accounts, and the vendor separately describes its model as pricing per lead rather than per email sent.

Checked 2026-09-23

Billing pairs an annual licence with a monthly compute credit allowance and a sub-account count, and the vendor quantifies consumption at roughly fifty credits per task run and twenty per image.

Checked 2026-09-27

Billing is metered per end-user conversation rather than per seat, with a resolution-based alternative offered to enterprises that ask for it; no rate per conversation is published.

Checked 2026-10-11

Billing is per engagement in phases - teardown, pilot, production deployment, enterprise programme - with third-party usage, infrastructure and support called out as separate lines, but no rate, day rate or unit price is published.

Checked 2026-10-03

The vendor charges nothing at all, so your only running cost is the model provider tokens your agent consumes, which the shipped cost guard meters per run.

Checked 2026-10-11

Billing is per team seat and per live AgentOS connection; the vendor meters no events, tokens or egress because you own the compute.

Checked 2026-10-11

One meter only, the conversation: each plan is a prepaid block, extra conversations bill at the plan rate ($0.50 on Starter down to $0.30 on Scale), and seats are never charged.

Checked 2026-09-23

Billing is a monthly plan fee plus a consumable USD balance: plans grant a monthly amount and top-ups carry a sliding service fee, with credits charged per action.

Checked 2026-10-03

The tool itself costs nothing; what you pay is token consumption at whichever LLM provider your key belongs to, and the docs treat context size as a direct cost to you.

Checked 2026-09-30

Billing is per seat with metered credits layered on top: each plan includes a fixed number of users and a per-user annual allowance of email and phone credits, and enrichment burns 0.5 credits a call whether run in-app or over MCP.

Checked 2026-09-10

Billing is subscription quota first, then metered AI credits at Agent Platform consumption rates, or pure consumption billing for organisations; nothing is priced per seat in the CLI itself.

Checked 2026-09-10

Billing is per validated contact in credits, with a seat and campaign-email allowance on plans: counts and masked previews cost nothing and undeliverable rows are filtered before they are charged.

Checked 2026-09-26

Pricing is per scoped engagement with a published target range, and third-party model, hosting and support spend is estimated on top rather than bundled.

Checked 2026-10-03

Priced by monthly credit allocation rather than per seat, with published per-action rates and a rough 20-credits-per-prospect campaign figure; mailboxes, phone numbers and dialer seats are billed separately in dollars.

Checked 2026-09-10

Billing is metered per minute per consumed service, so a bot connection, speech service, voice channel and LLM tokens are each charged separately rather than by seat.

Checked 2026-09-24

Metered in dollars: LLM tokens at provider list price, a 40% service fee on LLM, and $0.19/hour Cosmos compute.

Checked 2026-09-02

The framework itself carries no meter at all; your only spend is whatever your chosen model provider bills against the API key you supply.

Checked 2026-09-19

Two meters, both published: a flat monthly price per connected lead source or phone number, plus voice billed per talk minute, so cost tracks channels activated and minutes spoken rather than seats.

Checked 2026-09-11

Billing is by project or by engineer time rather than per seat or per token, but only the three fixed-price automation packages carry a published figure; time-and-materials rates appear nowhere.

Checked 2026-09-11

Billing is per connected minute, prorated to the second, with a separate transfer-minute rate rather than seats or tokens.

Checked 2026-09-11

Billing is metered in AI tokens against a monthly allowance, with Teams charging per member on top; project size drives consumption per message.

Checked 2026-09-11

Metered per conversation, not per seat or per token: extra conversations come in packs of 100 and LLM spend is included at $0.10 per conversation, above which credit grants are auto-purchased at cost.

Checked 2026-09-02

Metering is per message expressed as credits, with a fixed monthly allowance, separate voice minutes, and a per-client seat charge on top for agencies beyond the five included.

Checked 2026-09-13

Monthly plan fee plus pay-as-you-go overages metered per browser hour, per GB of proxy and per 1k API calls.

Checked 2026-09-02

Two meters: credits for the models (about 1 credit per TTS character, 3 credits per second of Ink-2 audio) and per-minute US dollars for agent calls.

Checked 2026-09-02

Metered per million tokens against an API key, with cache-write, cache-read and output rates priced separately.

Checked 2026-09-02

Two meters: a per-seat usage allowance on subscription plans, or per-token billing on the Console and cloud providers.

Checked 2026-09-02

Three shapes coexist: metered credits per model call, one flat monthly subscription for curated open-weight models, or your own provider bill under BYOK - and no seat fee on the open-source client.

Checked 2026-09-12

Billing is a per-developer seat plus optional metering: over-limit reviews at a fixed price per reviewed file, and cloud agent work billed by the minute.

Checked 2026-09-15

Per-token consumption expressed as credits per 1M tokens on ChatGPT plans; API-key auth bills raw API tokens.

Checked 2026-09-02

Billing is a monthly plan with an included automated-DM allowance plus a published per-DM overage rate that falls as the plan grows; keyword monitoring and public replies are never metered.

Checked 2026-09-28

Billing is per resolution — $1.25 for AI-handled, $2.25 for the AI-plus-human model — but the fixed monthly fee charged alongside it is never quantified, so only half the unit is public.

Checked 2026-09-12

Cresta names its pricing dimensions - products, agent count, conversation volume, channels and languages - but publishes no rate, no unit price and no overage figure, so cost is quoted per deployment.

Checked 2026-09-13

Metering is per workflow execution rather than per seat, and the free tier states its allowance, but Enterprise volumes are sized case by case with unpriced overage.

Checked 2026-09-13

Two meters at once: a seat or plan subscription, plus token usage from two pools priced per million tokens, with on-demand overage billed in arrears.

Checked 2026-09-02

Billing meters customer contact, not seats: a fixed rate per incoming conversation, or a higher rate per resolution with escalations free.

Checked 2026-09-14

Metered per minute of WebSocket connection time, one rate covering STT, LLM and TTS together; the tier depends on which LLM you pick and whether you bring your own LLM or TTS. Billing is true per-second, not rounded up.

Checked 2026-09-02

Metered by the work performed: plan quota then prepaid on-demand credits self-serve, Agent Compute Units on Enterprise.

Checked 2026-09-02

A subscription (plus per-seat on Teams) buys a token-metered daily and weekly quota; overflow is billed at API list prices, and Enterprise contracts meter in Agent Compute Units.

Checked 2026-09-03

Per-workspace subscription with a seat ceiling, metered in message credits: one credit-consuming AI response per model call, priced by model.

Checked 2026-09-02

Billing is per seat with a monthly credit allowance per seat type, and non-human usage is metered separately at a published per-credit rate on Business.

Checked 2026-10-01

A monthly plan buys included call minutes and concurrency; overage is per minute, texts are per message, and LLM plus telephony are billed on top at usage.

Checked 2026-09-02

Billing is per seat per month, but the work itself draws on a monthly usage pool whose size Elicit never states in any unit; overage is sold in fixed $100 increments of extra usage.

Checked 2026-09-14

Flat monthly price per device, with the plan deciding how many phones you get; the vendor explicitly rules out per-minute or per-session metering.

Checked 2026-10-09

Two meters at once: a monthly plan that grants credits, and credits consumed per video at creation, priced 20 to 100 by model with top-up packs sold separately.

Checked 2026-10-03

Per-seat subscription with rolling rate limits; model usage draws Standard Credits at per-model multipliers, then prepaid Extra Usage.

Checked 2026-09-02

Billing is per resolved outcome rather than per seat or per token, with a second, ten-times-higher rate for sales qualifications and no charge for a conversation simply passed to a human.

Checked 2026-09-18

Billing is credits consumed per request, not seats: one credit per scraped page, two per ten search results, with documented add-ons.

Checked 2026-09-24

Two meters run side by side: a per-seat subscription with unlimited chats and skills, plus pooled credits for API and MCP work priced per operation, so programmatic volume is billed separately from headcount.

Checked 2026-09-14

Per seat per month, monthly or 12-month commitment, billed monthly either way. Consumption is capped by per-user daily request quotas rather than charged.

Checked 2026-09-02

Consumption is metered in credits that scale with model tier, output length and task complexity, layered on a $30 per-seat monthly charge on Team and a separate flat Cloud Computer fee for Claw.

Checked 2026-09-15

Per user per month for a seat, plus consumption metered in AI credits at one cent each; completions and next edit suggestions are unlimited and free of credits on paid plans.

Checked 2026-09-02

Per-user monthly seat, plus metered consumption on top: pooled FlexCredits under Enterprise Flex, or per-million-token Model Hub Usage under Core Suite.

Checked 2026-09-02

Nothing is metered today because the whole research product is free with no card; the vendor says paid plans are coming but publishes no seat, credit or usage unit for them.

Checked 2026-10-05

The framework meters nothing. You pay the model provider whose key you supply, plus Google Cloud's Agent Runtime beyond its no-cost tier if you deploy there.

Checked 2026-09-02

goose itself charges nothing, so the running cost is entirely your LLM provider's metered token or credit spend; no calculator or cost estimate is published and the vendor only tells you to keep provider credits topped up.

Checked 2026-09-16

The vendor bills nothing at all; cost is per research run of LLM and retriever spend, and its own published estimates range widely.

Checked 2026-09-16

Billing is credit-metered on top of a flat plan fee: model tokens, compute and paid tool calls at list price, plus an 8% orchestration fee, with credits priced at half a cent.

Checked 2026-09-30

Billing is per minute of talk time, metered by the second against a monthly credit balance, on top of a flat plan fee. It is explicitly not per seat, and carrier charges are passed through separately.

Checked 2026-09-10

Paid plans are flat per-month subscriptions, with Team charged per seat and each tier capping connected devices and storage.

Checked 2026-09-29

The published Standard plan is a monthly fee that scales with query volume, while the Managed Resolution line charges per resolved conversation with no seat or platform fee.

Checked 2026-09-24

Billing is a per-account recurring subscription from $29/mo, but payments are also recorded as credit grants and the CV tool sells a one-time unlock, with no credit rate published.

Checked 2026-09-14

Juggler itself meters nothing and charges nothing: your spend is whatever your model provider bills against the subscription or API key you bring, so cost tracks token usage rather than seats or tasks, with no vendor-side calculator.

Checked 2026-09-17

Billing is a monthly plan that carries a credit allowance, and every action draws on it at a rate set by task type, chosen model and complexity rather than by seat alone.

Checked 2026-09-17

Two meters stack: a per-user seat, then AI Credits consumed by agent work, each credit pegged to a dollar. The bring-your-own-key path drops the credits and bills you at provider rates.

Checked 2026-09-18

Billing is a fixed monthly subscription chosen by team size plus metered voice usage at €0.19 per minute of actual assistant conversation time, with no prepaid minute bundle and the same rate on every plan.

Checked 2026-09-26

Three meters: per seat for the platform plan, provider token rates for inference, per second for cloud compute.

Checked 2026-09-02

Billing mixes a per-seat licence with pay-as-you-go consumption: traces beyond the included allowance, plus compute units for Engine, Fleet, deployments and sandboxes.

Checked 2026-09-18

Two meters at once on the managed platform: a per-seat licence at 39 dollars per seat per month, plus consumption in LangChain Compute Units (1.50 dollars) and Storage Units (1.00 dollar). The library itself is free.

Checked 2026-09-02

Two meters on top of a monthly subscription: enrichment and scoring consume credits with a published per-action price list, while drafting draws on a fixed monthly AI budget the vendor says avoids overage.

Checked 2026-09-18

Two of the vendor's own posts price it per conversation minute plus a monthly platform fee, but the pricing page publishes no rate card and a third post calls the model 'per-seat', so the metering a buyer actually signs is not settled.

Checked 2026-09-09

Per seat on personal and Teams plans; the API plan meters per active agent, per second of tool execution and per token.

Checked 2026-09-02

Two meters run at once: a per-user seat price, and credits consumed only while Lindy works, priced at roughly a cent each with published bands of 2-250, 250-1,000 and 1,000-2,500 per job.

Checked 2026-09-19

Billing is per deliverable rather than per seat or per token: two fixed-price units are published, $8 for a single question and $20 for a deeper brief, each with its own source count and turnaround.

Checked 2026-10-10

Monthly plan fee plus consumption: $0.01 per agent-session minute, per-token LLM, per-1M-character TTS, per-minute STT and telephony. Each plan bundles an allowance before overage starts.

Checked 2026-09-02

Metered in credits billed per page (or per minute of audio) at $1.25 per 1,000 credits.

Checked 2026-09-02

A per-agent monthly subscription carries an included allowance, then meters: per-minute voice overage and per-active-minute connector charges stacked on the base fee, with carrier fees passed through.

Checked 2026-09-09

Billing is per credit, burned by LLM tokens, cloud VM time and third-party API calls, on top of a per-month plan or a per-seat Team price; hosting a built site is metered separately.

Checked 2026-09-19

Plan fee plus consumption metering: observability events, CPU hours, egress, memory tokens, retrieval storage and database rows all have per-unit overage rates. Not per seat.

Checked 2026-09-02

The vendor names resolution volume as what the price scales with, but publishes no per-resolution rate; the contract meters against a subscription usage allowance with overage priced privately in the order form.

Checked 2026-09-03

The framework itself costs nothing, so all spend is model and tool consumption metered by whichever provider you configure; Microsoft publishes no calculator and states the usage cost is yours.

Checked 2026-09-19

It is a seat-style subscription with pay-per-use model spend layered on top, metered in tokens and quoted per million tokens, and the vendor states it adds no markup.

Checked 2026-09-20

Billing is a flat monthly plan with usage allowances rather than seats: conversations, connected channel accounts and AI messages are metered, with extra AI messages sold in packs and WhatsApp fees billed by Meta.

Checked 2026-10-03

Billing is per credit, deducted from weighted token usage with per-mode minimums, so Build turns cost more than Ask turns.

Checked 2026-10-09

The one published figure meters per user per year on a 12-month contract; moveworks.com names no unit at all and routes buyers to a custom quote.

Checked 2026-09-02

Two metering models: pay-as-you-go per input, cached and output token, or a flat monthly subscription tied to the CLI's own key with prompt allowances instead of tokens.

Checked 2026-09-20

Metered per workflow execution, where one execution is one full run of a workflow regardless of steps or data; users are unlimited and AI Assistant credits are a separate monthly allowance.

Checked 2026-09-02

Two units stack: a per-person monthly subscription, and one auto-apply credit consumed per application, with 150 credits on Pro and 450 on Max.

Checked 2026-09-29

Two meters at once: a flat per-month plan price, plus agent usage billed at two cents per use from prepaid credit blocks.

Checked 2026-10-08

Billing is a flat monthly prepaid balance drawn down per minute of conversation, with per-message rates for chat and WhatsApp and published overage rates on every tier.

Checked 2026-09-09

The framework itself is charged for in no unit at all, being MIT-licensed and free; what a buyer actually pays is their model provider's token metering plus any hosted tool usage, billed outside this product.

Checked 2026-09-20

Pay-as-you-go per token, with audio metered at 1 token per 100 ms of user audio and 1 token per 50 ms of assistant audio; translation and transcription sessions bill by audio duration instead.

Checked 2026-09-02

The agent itself is free; inference on the vendor's Zen gateway is metered per token, while the enterprise offer is priced per seat instead.

Checked 2026-09-21

Not seats: you pay for model tokens, either with your own key or through the vendor's proxy billed per million tokens at provider rates.

Checked 2026-09-21

Consumer and Enterprise plans bill per seat per month, Computer meters credits per seat, and the API bills per token plus a fee per tool invocation.

Checked 2026-09-02

Two meters at once: a monthly plan fee that includes a dollar-denominated credit allowance, then consumption billed per agent response at live per-model rates.

Checked 2026-09-09

Billing is per credit consumed by work that finished, with monthly credit allowances on the paid tiers rather than per-seat pricing.

Checked 2026-10-03

Metered by conversation volume, not seats: the MSA credits two CX Tokens per call minute and one per chat, with call time rounded up to 30-second increments.

Checked 2026-09-02

Precision places itself in the partner-delivery column of its own comparison table, whose cost line is a build fee plus run costs and support; no rate, retainer or unit figure is published.

Checked 2026-10-06

The framework charges nothing per seat, task or token; your spend is model inference, paid either straight to providers with your own keys or through the vendor's Gateway, which adds a markup on built-in providers.

Checked 2026-09-21

Custom quote with no published metering unit; the only visible cost dimensions are tier gates on websites, contact-database volume and production instances.

Two meters plus seats: an Action is one tool run, Vendor Credits are the pass-through model and tool cost, and each plan caps how many build users it carries.

Checked 2026-09-22

Billing is a subscription plus effort-based credit consumption per completed checkpoint, with third-party model calls passed through at provider rates.

Checked 2026-09-22

Billing is consumption-based: voice agents bill per call minute split across voice infra, model and telephony, chat agents bill per AI message, with named add-ons metered per minute or per dial.

Checked 2026-09-23

One flat monthly subscription for the whole account with no seat counting, and ad budget paid separately to the ad platforms rather than to Revnu.

Checked 2026-10-11

Billing is a flat monthly plan with a bundled pool of call minutes, then metered per-minute overage at a published rate that falls as the plan rises; nothing is charged per seat or per token.

Checked 2026-09-09

Per-action metering on top of a monthly allowance, with a published rate card: 2 actions per news insight, 6 per sequence output, 23 per deep Clever Column cell, 15 per connected dial-minute, variable actions per token for chat.

Checked 2026-09-03

Billing is a monthly retainer or planning budget plus a separate one-off setup fee, with model usage, hosting and Meta message charges quoted on top rather than metered per seat or per task.

Checked 2026-09-28

Consumption is metered per action against a Flex Credit pool: 20 credits per Agentforce action, 30 per voice action, 100k credits for $500. Per-user licensing and a flat $2 per conversation are the alternatives.

Checked 2026-09-03

Billing is a flat subscription per connected LinkedIn account rather than metered credits, tokens or per-task charges; the first account is included.

Checked 2026-09-25

Billing is per article credit inside monthly plans rather than per seat: each tier buys a fixed number of articles per month, and agencies buying 300+ get a per-article rate.

Checked 2026-09-25

A monthly plan bundles sites and seats with one shared AI credit pool; publishing and no-AI template pages are never metered and overages are never auto-charged.

Checked 2026-10-03

Billing is per achieved outcome rather than per seat or per token, which Sierra states as its deliberate business model.

Checked 2026-09-26

Per seat per month plus metered credits: 1 credit = $0.005, 1 credit per run plus model tokens.

Checked 2026-09-03

Billing is per talk minute: four prepaid minute packages, each with a published per-extra-minute rate and no base fee, cancellable monthly.

Checked 2026-09-03

Billing is a flat monthly price per organization with audit and schedule quotas attached, so the metered unit is an audit run rather than a seat, a token or a credit.

Checked 2026-10-03

Billing is a flat subscription per account rather than per minute or per task, with plan tiers metered by number of AI agents, phone numbers and monthly minutes.

Checked 2026-09-26

Two meters at once: a per-user seat price plus a workspace credit balance drawn down per enrichment, briefing, agent run and generated table cell.

Checked 2026-09-15

Consumption is metered in runs, where a run is one workflow execution; seats and projects are counted separately and the Enterprise run allowance is negotiated.

Checked 2026-09-09

Calls are metered per second and aggregated into billed minutes; chat converts at 5 AI messages per usage minute.

Checked 2026-09-03

Enterprise is priced per user per month plus storage per terabyte, with model inference billed separately by whichever AI provider you connect.

Checked 2026-10-03

Billing is per scoped build with a fixed entry fee, then ongoing provider costs passed through: voice API and phone line usage sit on top of the one-off setup charge.

Checked 2026-09-12

Billing follows conversation time, not seats: a platform base fee of $0.08 per minute plus metered telephony, LLM, STT and TTS, with WhatsApp and WeChat messages priced per message.

Checked 2026-09-16

Billing is per consumed minute for the voice engine, per token for the LLM and per minute for telephony, with no seat or platform fee, so cost tracks call volume rather than headcount.

Checked 2026-09-09

Metered per agent step and per browser-minute against a prepaid Wallet; Search and Fetch are free.

Checked 2026-09-03

Two meters at once: named-user seats plus consumption units drawn per LLM call inside an agent run, charged in 64k input-token increments, with customer-managed models instead billed once per agent run.

Checked 2026-09-03

Billing is per person per month on a plan, with compute rather than credits as the differentiator between Free, Pro and Enterprise tiers.

Checked 2026-09-26

Billing is a per-seat monthly fee plus a credit allowance consumed per action, with fractional rates published per feature.

Checked 2026-09-27

Per call minute for Vapi hosting, plus model provider cost passed through at cost, plus $10 per concurrent line per month.

Checked 2026-09-03

Two meters at once: a flat annual membership that buys member rates, then consumption billed per million tokens and per unit of compute, storage, speech and parsing.

Checked 2026-09-27

Two meters at once: a monthly subscription for machine, storage and an included usage bundle, plus pay-as-you-go credits where one credit equals one US dollar of provider cost.

Checked 2026-09-27

Billing is a flat monthly or annual subscription per plan with pooled minute allowances, explicitly not per seat and with no activation fee; extra lines are a fixed monthly add-on.

Checked 2026-09-22

Priced per call minute: each plan bundles an allowance and meters overage per minute, cheaper as the plan rises.

Checked 2026-09-03

Billing is prepaid minutes on a monthly plan, not seats and not per call: 500, 1,000 or 2,000 included minutes, with the vendor publishing approximate call equivalents of ~200, ~400 and ~800.

Checked 2026-10-03

Metered in identification credits on top of a plan fee: one credit per company and one per contact, capped at two per unique visitor per month.

Checked 2026-09-03

Per-credit, on top of a per-seat subscription. A credit is token-proportional and non-deterministic, metered across inference, sandbox compute and platform, all drawing on one balance.

Checked 2026-09-03

Purely consumption-priced: you prepay credits and spend a per-run dollar budget, with per-operation and per-token rates published rather than a seat or subscription fee.

Checked 2026-09-27

The tool itself charges nothing; consumption is metered by whichever web AI account you sign in with, under that provider's own quota.

Checked 2026-09-21

Two units at once: a per-seat monthly subscription, and hosted model usage metered per token at provider list price plus ten percent beyond the included credit.

Checked 2026-09-29

Billing pairs a per-seat monthly fee with metered credits, where each model carries a published multiplier and extra credits are bought on demand at a $20 minimum.

Checked 2026-09-09

Two meters at once: per agent seat per month for the plan, plus per automated resolution beyond the plan allowance ($1.50 committed, $2.00 pay-as-you-go).

Checked 2026-09-03

The harness itself costs nothing and meters nothing; you pay your model provider per token or through an existing subscription, and zot only surfaces the running cost in its status line.

Checked 2026-09-28

Billing is per project or per developer-hour, not per seat or token: staff augmentation is quoted hourly by seniority while builds are quoted as fixed project ranges after scoping.

Checked 2026-09-25