DocsFlowcy Agent Billing
Model access is restricted to enabled database entries. Administrators manage aliases and USD-per-token prices in Settings → Flowcy Agent Models. Gateway supplies default input, output, cache-read, and cache-write prices; configured prices determine the account charge.
The chat endpoint requires Rx Subscription's settle_usage_v1 capability. Deploy the subscription service before deploying this chat route. Missing capability or an unavailable meter denies admission.
Before generation, the server reserves the cost of the model's full advertised context window at the highest configured input price, plus at most 4096 output tokens (bounded by the advertised maximum). This deliberately conservative reservation can reject a model even when a smaller prompt would fit. All three meters must accept the reservation. Partial admission failures release or tombstone every attempted reservation. Automatic SDK retries are disabled.
Successful generations settle each meter to the reported token cost, rounding up once to integer micro-USD. Cache-read/write tokens are removed from ordinary input totals; output already includes reasoning. Settlement only reduces the original reservation and is idempotent. A settled reservation cannot subsequently be released in full.
If generation is interrupted, usage is unavailable, or settlement fails, reserved quota remains held. There is currently no automatic reconciliation worker. Administrators must investigate unresolved reservations; do not indiscriminately refund them because provider work may already have occurred. This limitation must be addressed before general release.
Plus costs $10/month and grants $3/5 hours, $7/7 days, and $15/30 days. Meter keys are agent_cost_5h, agent_cost_7d, and agent_cost_30d; 1 USD equals 1,000,000 units. Limits and reset policies are managed in Rx Subscription rather than hardcoded in chat.
Agent Pro is a draft $40/month plan with $50/30 days. Its shorter-window allowances are not configured; defaults are zero, so it cannot yet use this route. No top-up product has been created: purchase price, credit amount, and expiry need a product decision.
Focused unit tests cover pricing, admission failure cleanup, unavailable settlement capability, concurrent quota denial, and retention on settlement failure. Subscription database tests cover atomic quota changes, idempotent settlement, and refund prevention. These are not evidence of deployed Gateway billing or production database migration success.