Platform scope and applicability
Token Pyxis provides model access, routing, usage metering and permissions exclusively to enterprises with signed service agreements and their authorized users. The operator provisions enterprise accounts after signing, and enterprise administrators assign member access. The public can browse the website, model catalog and documentation. Public self-signup and consumer services are unavailable.
The Interim Measures for Generative AI Services define scope according to the audience served and include services provided via programmable interfaces. When an enterprise integrates models into an application serving the public in mainland China, assess applicable filing or registration, labeling and complaint-handling requirements based on the audience, deployment and each party’s role.
Terms and account permissions · Interim Measures for Generative AI Services, Articles 2 and 22
Filings, licenses and verification
Filing, registration, licensing and assessment duties depend on the operator, deployment and service. Use the verification paths below. This site has yet to publish verified operator details, filing identifiers or license evidence. Check the contract materials and regulator records during procurement.
- ICP filing or operating license
- Determine the applicable filing or licensing requirements for the service. Internet Information Services Measures · MIIT filing lookup
- Public-security filing
- Verify filing and disclosure using the production website, its operator and the relevant local requirements.
- Algorithm filing
- For services in scope, verify algorithm filings and any amendments or cancellations. CAC filing system
- Generative AI filing or application registration
- Check local requirements. Applications or features that directly call a filed model should verify applicable registration and launch disclosure requirements. CAC notice on filings and registration
- Security assessment
- Where applicable, including services with public opinion attributes or social mobilization capabilities, complete the required assessment and procedures. Interim Measures, Article 17
Labeling generated and synthetic content
- Gateway response signal
- The data plane adds
X-AIGC-Label: AIGC-generatedby default so an integrating application can recognize and display a notice. Verify HTTP response signals and implicit metadata embedded in files separately. - Display, export and publication
- Where required, add a visible label in the interface or relevant medium, preserve labeling through download, copy and export, and declare generated and synthetic content when publishing it online.
- File metadata and label integrity
- For services handling files with generated and synthetic content, verify embedded labeling against applicable rules and GB 45438-2025. Malicious removal, alteration, fabrication or concealment of labeling is prohibited.
AI-generated and synthetic content labeling measures · GB 45438-2025
Log retention and data protection
Where applicable law requires related network logs to be kept for at least six months, configure retention for the statutory period. The software default for request logs is 180 days. Check the deployment’s actual archive and cleanup rules and assess metadata, diagnostic capture, audits and financial records separately.
When content without a visible label is lawfully supplied to a specific user under an agreement, verify separate retention of the relevant recipient records under Article 9 of the labeling measures. Diagnostic payload capture is off by default. See the privacy policy and data security page for capture and access controls.
Content governance and integration responsibilities
The platform provides configurable content rules, permissions, usage controls and security auditing. Configure and review controls for the service context. If unlawful activity or a security incident is identified, take required action, preserve relevant records and report where applicable.
Downstream applications should protect personal information and intellectual property, notify users and review generated content. Services subject to minor protection duties should implement controls relevant to their use. Verify terms, providers and regions for selected upstream routes.
Interim Measures, Articles 9–15 · Review data security controls
Complaints and reports
Enterprise service feedback
Enterprise customers can submit billing, content or security concerns through the support contact in their agreement or ask their administrator to forward them. This site has yet to publish a public operator complaints email.
Include the enterprise, issue category, time, request ID or public URL, and necessary evidence. Redact API keys, passwords, session credentials, personal information and sensitive payloads. Handling and response periods follow applicable law and the enterprise agreement.
Illegal or harmful online content can be reported through the official reporting channel. See the privacy policy to exercise your data rights.
