Platform billing
opheli.ai subscriptionThis covers the product itself.
Account
Billing and BYOK
Billing in opheli.ai has two layers: the platform subscription and any model usage billed by your connected provider when you use BYOK.
Guide summary
Use this page to understand the surface before you act inside it.
Understand the difference between your opheli.ai subscription, BYOK provider usage estimates, plan limits, and Mock Mode.
Guide type
AccountThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
4Written against the current product structure and core execution workflow.
Model billing
Your provider accountBYOK usage is billed by the connected provider, not by opheli.ai.
Related action
Check Billing before supportLimit or budget issues often explain blocked work faster than troubleshooting a run first.
Guide section
What it is
Billing and BYOK explain what the platform covers, what your provider covers, and how limits affect execution.
When to use it
Use it when setting up BYOK, investigating blocked work, reviewing usage, or considering an upgrade.
Where to find it
Find it in Billing, Provider Vault, and cost-aware run surfaces.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Assuming opheli.ai pays model usage
Related action
Use the “Budget or plan limit reached” guide when a blocked action looks cost-related.
Guide section
Why it matters
This prevents confusion about provider billing responsibility and helps users recover faster when limits block progress.
Guide section
How it fits into the workflow
Billing posture shapes whether live execution can continue at all.
Guide section
Step-by-step usage
- Review your platform plan.
- Confirm whether the run is using BYOK or Mock Mode.
- Check provider usage estimates and budget posture.
- Review any plan or budget limits in the product.
- Escalate to upgrade or support only after you know which layer is blocking you.
Guide section
Inputs and outputs
Inputs needed
Platform plan
Provider posture
Usage and budget state
Outputs produced
Clear provider-billing responsibility
Fewer false bug reports
Better recovery decisions
Guide section
Common mistakes
- Assuming opheli.ai pays model usage
- Ignoring budget guard signals
- Blaming a failed run when the issue is really plan or provider posture
Guide section
Troubleshooting
If work stops at a limit, check whether the blocker is plan limits, provider usage estimates, a budget guard, or provider access.
Guide section
Estimated versus provider-verified costs
Costs shown in opheli.ai are estimates unless a usage record is explicitly marked Verified by Provider.
External Providers determine final charges, free-tier limits, credits, discounts, taxes, and invoices. opheli.ai does not control those provider billing rules.
Use opheli.ai estimates and budget guards as planning signals, then verify final usage and billing in the connected Provider dashboard.