Common objections
Top 5 objections to outcome-based billing, answered
How do you prevent gaming of "success" outcomes?
Outcomes are resolved via your own /v1/outcomes call tied to a server-side event your customer actually acknowledged, not a self-report from the agent. Idempotency keys on outcome_id prevent double-counting, and any outcome you resolve as success is stored immutably with the meter event so retrospective edits can't rewrite history.
What if outcomes are hard to define for my agent?
Outcomes don't have to be binary. You can leave outcome_bonus at 0 and bill purely on base + token rate, define outcome as a custom enum (booked, replied, qualified, rejected, expired), or set a generous expiry window so unresolved runs auto-fall to expired and only the cheap components bill.
How is this different from usage-based pricing?
Usage-based pricing bills every request the same flat rate regardless of value. Rev's three-component stack charges a small base + token fee for every run, then an outcome bonus that only posts when the run resolves as success — so you earn on customer wins, not on call volume, and refunds are automatic on failure / expired.
What happens if my agent's confidence is low on a run?
Confidence is your product signal, not Rev's. If your model returns low confidence you decide the outcome state yourself: resolve as failure to skip the bonus, leave it pending until a human reviews it within your expiry window, or treat it as success and tune the bonus rate accordingly. Rev's pricing engine only knows the outcome you POST, never the model's score.
Can I switch tiers mid-cycle?
Yes. Upgrades take effect immediately and are pro-rated by Stripe; downgrades take effect at the next billing cycle. Pricing tier changes never retroactively rewrite historical price_charged values stored on meter_events, so past bills stay auditable.
Frequently asked questions
Is Rev usage-based pricing?
Rev is outcome-based, not raw usage-based. Every plan includes a monthly base (or event cap) plus a free dev tier; usage above the cap rolls into the next tier rather than billing per call.
How does outcome-based billing compare to per-call pricing?
Per-call charges the same flat rate for every run regardless of result. Rev charges a small base + token fee for every run, then a separate outcome bonus only when the run resolves as success. You earn on wins, not on attempts.
What's included in the Rev free tier?
The free tier ships with 1,000 metering events per month, full access to the metering API and outcome engine, dashboard analytics, and webhook delivery — no credit card required.
Are there per-seat or per-API-key limits on paid plans?
No per-seat fees. Paid plans are capped by monthly metering volume: Starter 10k, Growth 100k, Scale 1M. Multiple API keys are allowed per workspace.
What happens if I exceed my monthly event cap?
Events above the cap continue to be accepted. Over-cap events are tagged for billing in the next period and surfaced in the dashboard so you can either upgrade your tier or throttle at the client.
Can I change plans mid-month?
Yes — upgrades take effect immediately and are pro-rated by Stripe. Downgrades take effect at the next billing cycle.