Temporal Continuity API / Beta Phase 31.1
Beta Testing
Install → Key → Connect cognition → Build
Join Beta TestingBeta credits
10,000 Continuity Credits per month. One Continuity Credit equals one turn with temporal continuity. The allotment resets monthly. There are no automatic paid overages. Edge cases can request additional credits; additional credits are discretionary during beta.
Beta community
Join the Temporal Continuity Beta community on WhatsApp to connect with other beta testers, share what you build, and discuss testing.
Beta reporting
Use the Beta Test Console for: Bug · Installation problem · Unexpected behavior · Performance/reliability · Feature request · Something interesting happened · Show us what you built.
Beta expectations
- This is beta software and interfaces may change.
- There is no production SLA during beta.
- Beta credits have no cash value and there are no automatic paid overages.
- When credits are exhausted, continuity turns stop until the monthly reset or additional beta credits are approved.
- Do not submit secrets, credentials, or private relational content in beta reports.
- Breaking changes may occur during beta; material integration changes will be identified in beta documentation.
- Beta participation, terms, credit allotments, and availability may be modified or concluded.
Data export/deletion capabilities and the complete beta privacy terms will be stated here before external beta enrollment opens.
Understanding Temporal Continuity
Durable relational state belongs to the Temporal Continuity API relational layer.
It mediates cognition and forms the contribution Temporal Continuity needs without becoming another persistence layer.
The Temporal Continuity API isn't tied to a particular model provider. The cognition provider can change without transferring ownership of the relationship's history to that provider.