Product-Specific Terms

Required coverage

• Subscription packages and included capacity.
• Usage metering, credits, top-ups, overages, refunds, and expiration posture.
• Pilot scope, implementation services, deliverables, and acceptance criteria.
• MCP/API access, agent capacity, rate limits, and customer responsibilities.
• Support, maintenance, beta, preview, and feature availability disclaimers.

Packages and capacity

• Each package should define included workspaces, enabled product areas, monthly usage credits, support level, automation level, and concurrency limits.
• Capacity may include agent runs, workflow executions, reports, source captures, storage, model usage, MCP/API calls, social publishing, enrichment, and marketplace or supplier-backed services.
• Unused credits, top-ups, overages, expiration, refunds, downgrades, upgrades, and carry-forward rules must be explicit.

MCP, API, and third-party clients

• MCP/API access may be subject to authentication, rate limits, package entitlements, audit logs, additional fees, and acceptable-use controls.
• If customers use Claude, OpenAI, custom agents, or other clients to operate Omega, the customer remains responsible for that client, its terms, and authorized use.
• Omega should preserve authority, telemetry, cost, and evidence boundaries even when work is initiated through external clients.

Revenue recognition and billing evidence

Commercial terms should align with Aureus billing, subscription state, package taxonomy, entitlement resolver, usage metering, invoices, taxes, refunds, deferred revenue, and revenue-recognition evidence.