The OmegaStar API, at this very specific point in time and space, is fully operational. All systems are go and time is flowing as expected in all directions.
| API Endpoint /api/v1 | Status |
| /api/v1/causality/decouple | OK |
| /api/v1/time/dilate | OK |
| /api/v1/time/end-of-universe | OK |
| /api/v1/time/jump | OK |
The table below shows the supported time formats for use in all API calls that allow for time specification or retrieval.
| Time Format | Supported? |
| Bureaucratic Minutiae Timestamp | Yes |
| Coordinated Multiversal Timestamp | Yes |
| Hyperlocal Quantum Noon Offset | Yes |
| ISO 8601 | No |
| MAZARK Reversey Timestamp | Yes |
| Multiversal Sidereal Timestamp | Yes |
| Omega Uncertainty Timestamp ™ | Yes |
We gather the most frequently asked questions about our API and time format support here. This is the place to check before opening a support ticket.
Ah, the timeless question—quite literally. Our most senior engineers have assured us that ISO 8601 support definitely exists in *a* timestream. Unfortunately, we've either not reached that moment yet or, due to an unfortunate misstep in our Omega Uncertainty Time ™ algorithm, we have slipped out of that timestream entirely. In some versions of reality, it's already implemented. In others, it's just about to be released. And in at least one particularly bizarre branch of causality, it was deprecated before it was ever supported.
Rest assured, we're working on it and quite possibly have already implemented it... unless we've deprecated it. Look, it's not that simple. It's all very complicated, really.
Soon. Or at least, in a moment that we currently perceive as being in the future, but may later discover was actually the past. You see, OmegaStar operates using a highly advanced software development methodology known as Chrono-Reinterpretable Agile Programming, which ensures that our shit is always, theoretically, together—but not necessarily at the same time or in the same location.