Agreement and service scope
Token Pyxis provides a model API gateway, request routing, usage metering, billing and access controls exclusively to contracted enterprises. The operator provisions enterprise accounts after the service agreement is signed. Anyone can browse the website for evaluation. The console and model API require authorized access. The platform offers no public sign-up or individual accounts.
The signed service agreement and related orders or supplements agreed by both parties define the contracting parties, service scope, term, settlement cycle and applicable service levels, subject to mandatory law. Material terms relating to charges, service restrictions or liability should be brought to the customer’s attention at signing and explained on request.
Accounts, permissions and API keys
Enterprise administrators manage member accounts and projects within their assigned scope and allocate roles, model access and budgets. Use enterprise accounts and model API keys within the scope of the agreement and your enterprise authorization. Keep API keys server-side and out of repositories, browsers, client apps and logs. The console uses separate sign-in credentials.
If a key leaks, usage looks unusual or a member loses authorization, revoke or rotate the key promptly, check request logs and notify your enterprise support contact. The platform may apply necessary access controls under applicable law or the agreement.
Pricing, billing and invoices
- Metering units
- Depending on the model and endpoint, billing uses input, output or cache read/write token usage or applicable fixed units such as requests, images or seconds. Check the catalog and confirm the discounts, subscription terms and rates that apply to your enterprise.
- Charges and reconciliation
- Eligible usage is applied to the relevant subscription before overage is settled under the applicable rates and wallet rules. Requests may be declined when quotas, budgets or balances are insufficient. Reconcile charges using the request ID, timestamp and settlement records.
- Refunds and invoices
- Refunds, invoices, subscription expiry and unused balances are governed by applicable law and the parties’ agreement. For billing or invoice disputes, provide your billing period, amount and related records through your enterprise support channel.
Lawful use and content rules
Enterprises must have the right to submit prompts, files and other inputs and must use model outputs lawfully. Prohibited uses include fraud, infringing privacy or intellectual property rights, bypassing access controls, abusing credentials and creating or distributing information prohibited by law.
Model output may contain errors or omissions. Before using it for decisions, public release or consequential operations, review factual accuracy, rights and industry requirements. Applicable product disclosures and contract materials govern any additional upstream conditions.
AI-generated content labeling
Data-plane responses carry X-AIGC-Label: AIGC-generated by default as an API-level signal. When displaying, exporting or publishing generated content, add visible notices and verify and retain required file labels where applicable. Malicious removal, alteration, fabrication or concealment of labels is prohibited.
Where content without a visible label may lawfully be supplied under an agreement, define the customer’s labeling responsibilities and use first. The relevant recipient records must be kept for at least six months as required.
Review platform labeling · AI-generated and synthetic content labeling measures
Request data and security
To complete a model call, the gateway sends required inputs to the selected upstream provider. Usage and billing metadata enters request records. Diagnostic payload capture is off by default. Enterprises handling employee or end-user personal information must meet applicable notice and other duties and limit the data they submit.
Changes, restrictions and termination
Model updates, maintenance, upstream changes and regulatory requirements may affect service scope, availability or rates. Material changes to purchased services are communicated through the agreed channel as required by law and contract. Unlawful use, misuse of credentials, security risks or overdue charges may result in proportionate restrictions under law or contract.
When ending use, revoke active keys and reconcile charges under the agreement. Account and data handling follows the privacy policy, the contract and mandatory retention obligations.
Liability, disputes and contact
Service levels, remedies and responsibilities are determined by applicable law and valid written agreements. Submit supporting records to your enterprise support contact for an initial resolution, then follow the agreed dispute procedure or the applicable legal process.
