Contents
1. Program and availability
Project Zero is Tessen's developer intelligence preview program where separately enabled. These V1 terms supplement the Terms, Developer Terms and, where applicable, Node Terms. They do not announce that preview access is enabled for all users or that production capacity is available.
The program’s approved message is “THE ZERO POOL IS OPEN. MORE DEVELOPERS. MORE NODES. MORE INTELLIGENCE.” That messaging is not a guarantee of an individual entitlement, successful request or permanent free service. Program availability must be separately and truthfully presented in the access flow.
2. Eligibility and authentication
Access requires the identity, developer eligibility and entitlement checks actually implemented for the program. Device authorization must identify the requesting application and obtain valid approval. Do not approve a code you did not request or share credentials produced by an exchange.
Accounts may be restricted based on lawful program conditions, abuse prevention or available capacity. Project Zero availability is limited to the identities, entitlements and capacity actually enabled for the program. The current deployment’s free routes are disabled; metered routes being enabled does not establish public free-preview admission. Do not present planned enrollment as an established public launch.
3. Shared capacity and request outcomes
Preview requests share limited resources. A request may be queued, rate-limited, refused or fail when free capacity is unavailable. No specific model, token pool size, reset hour, throughput or uptime is guaranteed by these terms. Displayed accounting must be matched to server-authoritative program rules.
The intended preview is a zero-paid-routing program. Any fallback to a paid product requires separate, clear authorization under its commercial conditions; preview consent is not permission to silently charge. Program access, accounting and any fallback are enforced by the Gateway’s approved rules. The reviewed production configuration has ZERO_FREE_ROUTES_ENABLED=false and ZERO_METERED_ENABLED=true; any paid service requires its own disclosed authorization and billing conditions.
4. Allowances and credits
Allowances are program benefits subject to eligibility and use conditions, not a deposit, cash balance, transferable asset or investment. Do not promise redemption, exchange value or earnings without an actual approved commercial arrangement. Different preview and paid balances must be clearly distinguished.
Any program allowance or incentive is subject to the expressly approved entitlement and lifecycle rules. These terms do not promise a Node reward, exchange rate, cash redemption, transferable balance, numerical pool, payment rate or cash-out policy. Correcting an accounting error must be transparent and consistent with lawful accrued rights.
5. Permitted developer use
Use the preview for authorized development and evaluation within the Acceptable Use Policy and actual limits. Do not multiply accounts, spoof participation, manipulate metering or resell program access. Do not route around a capacity refusal or entitlement denial to unauthorized providers or paid services.
Evaluate generated code and protect project credentials. Free access does not mean data is public or that safety and privacy requirements are suspended. Production commitments to your customers must not rely on uncontracted preview capacity.
6. Node relationship
Voluntary Node participation may support the wider intelligence ecosystem or program incentives where implemented. It is not mandatory unless an actual, disclosed eligibility rule says so. Participating requires authorization to use the machine, energy and network resources involved.
Node terms govern resource use, privacy modes, workload handling and any approved credit mechanism. Project Zero membership does not authorize Tessen to execute arbitrary local workloads. Do not describe the program as cryptocurrency mining, guaranteed passive income or employment.
7. Data and feedback
Preview Input, Output and metadata are governed by the Privacy Notice, Developer Terms and any executed DPA. Model-provider conditions and content logging must be disclosed according to actual implementation. These terms provide no additional model-training permission and make no unverified promise about training exclusions.
Feedback should omit secrets, unnecessary personal data and customer-confidential information. Feedback is voluntary and should omit secrets and confidential or unnecessary personal information. Its permitted uses are limited to the feedback rights and evaluation disclosures in the approved agreement. A voluntary bug report is not unrestricted consent to reuse its content.
8. Changes, suspension and termination
Preview models, limits and availability may change, subject to applicable notice obligations. Tessen may pause access for security, misuse, technical constraints or program closure. Urgent protective suspension may be necessary; users should receive a review route where appropriate and lawful.
Program changes and discontinuation follow the approved notice process and preserve legally accrued rights and separately contracted services. Preview access does not guarantee perpetual availability. No indefinite access or migration period is promised. Stopping the preview does not automatically remove access to separately contracted Tessen services.
9. Support and related documents
The program carries no SLA or support response commitment unless separately agreed. Report failures with request identifiers and redacted diagnostics, avoiding tokens and credential files. For billing questions, distinguish preview allowances from paid usage in the request.
Read the Developer Terms, Node Terms, Acceptable Use Policy and Privacy Notice. Questions may be sent to hello@tessen.ai. The underlying agreement and mandatory law govern liability and disputes.