0.9.0: model services and shared plan allowances
Release pairing: Core 0.9.0 / MCP and Agent Client SDK 0.7.0 / DSH 0.7.0.
An enterprise assistant may choose a conversation model, generate a campaign image, then invoke an authorized business API. Administrators can give these models and generation tools a shared allowance. The local host continues to orchestrate the conversation and task; the Hub records original requests, actual usage and settlement. Existing business permissions and approvals remain in force.
What changes
Section titled “What changes”Optional model billing
Section titled “Optional model billing”Configure the actual provider connection and model, explicitly map a reference pricing model and endpoint, then create a plan for a personal or shared organization account. Conversation models and model tools have separate catalogs. Unready services stay out of callable entries; hosts can show the reason.
OpenRouter supplies reference prices, not the actual provider invoice. Each request preserves its reference price and plan multiplier; later price changes do not recalculate history. Charges are not based on user turns or task steps.
One plan, one allowance
Section titled “One plan, one allowance”An enterprise plan may sell for 300 USD and provide 100 USD per month at a 1.5 multiplier. A request with a 0.20 USD reference cost deducts 0.30 USD, leaving an actual allowance ratio of 99.70%.
- Periodic plans separate sale price from allowance. Daily, weekly or monthly resets restore the allowance; customers see a remaining percentage whose denominator is the period allowance.
- Credit packs provide a one-time USD allowance and display Credits at 1000 Credits per USD.
- Validity and reset periods are independent. The final partial period still has its full allowance; expiration stops new requests and unused allowance does not roll over. Template price edits do not reset original grant terms.
- Raw Token counts remain usage evidence. The business application owns payments, currency conversion, refunds and product pricing.
Image results and settlement are separate
Section titled “Image results and settlement are separate”Initial adapters support text-to-image through Aliyun’s OpenAI Images-compatible API, native DashScope and OpenRouter Images. Video, voice and custom capabilities may be declared but remain uncallable without an execution adapter.
Image requests persist dispatch records and finish asynchronously. Hosts query the original request ID. Completed results are usable while billing awaits actual metering; missing usage is never an invented zero fee. Late concurrent settlements may create an overage, and depleted balances block new requests.
Connection loss or an unknown result retains the original ID rather than creating another generation. Late usage after cancellation remains accountable and does not revive a finished turn. Image generation and a business update are separate actions; hosts can reuse their existing attachment space when needed.
Administration preserves original records
Section titled “Administration preserves original records”Removing a plan preserves historical grants, requests and the ledger. Disabled accounts can be archived and restored to the original disabled account without reviving old credentials or replenishing allowance.
Authorized administrators can reset an effective Hub-managed allowance. Periodic plans regain their original allowance with a new period anchor; credit packs regain their original Credits. Expiration stays unchanged and dispatched requests settle against their original pool. External backends retain ownership of the plans they provision.
Upgrade by role
Section titled “Upgrade by role”| Role | Action |
|---|---|
| Hub operator | Back up, upgrade Core and apply unapplied migrations 063 and 064 through the official migrator; optionally configure model connections, pricing, plans and accounts |
| Client host developer | Upgrade paired SDK/DSH, catalogs, summaries, persistent original requests and asynchronous results; verify resolved dependency versions |
| Business backend developer | Adopt separate issuer credentials and billing APIs only for provisioning or plan-scoped identity; preserve original idempotency inputs |
| User | Use an adapted host and retain existing business authorization; a plan grants no additional business write permission |
Upgrading public 0.8.0 requires no data purge. Run all unapplied migrations with npm run db:init; startup does not migrate automatically. Preserve configuration, secrets, databases and the migration ledger. Billing-preview installations separately verify their period allowance snapshots. See the paired upgrade guide.
Enable billing as needed; existing business tools, approvals, multi-account conversations, task controls, and archives remain available. After setup, check text streaming, image results, allowance summaries, and original-request recovery with your configured services, then review settlement records.