TIMEVERSE
Syncing T2°...
Timeverse
Docs

API Reference

Public Timeverse APIs for state, alignment, and evaluation. v4.6-compatible.

v4.6 Compatibility

This page follows Timeverse v4.6 principles: - Tick-canonical windows (integer ticks) - TV_MONO_NOLEAP arithmetic time (UTC is display only) - Canonical JSON signing (sorted keys, no whitespace) - Anti-replay (reject reused nonces/signatures)

Verified semantics vs Display-only

Important

Verified semantics are fields safe to sign/verify and use for security decisions. They **MUST** be integer-only (ticks, u16, fixed-point ints).

Display-only fields are for UI/logging. They may include floats/strings and **MUST NOT** be used for authorization or gating.

Authentication

  • Public
    endpoints: no API key required (rate-limited).
  • Paid
    endpoints: API key / pilot agreement.

1) Core State (Timeverse “Now”)
Public

GET `/v1/core/state`

Get the current Timeverse context required for IoT and multi-agent alignment: day anchor (`day_index`), phase ticks (`phi_ticks`), Harmony Segment (HS), coarse spatial context (SWT + Tile), and D-Calendar (C.Y.M.W.D).

Query parameters

ParameterTypeRequiredDescription
`swt_zone`int (1..12)OptionalLocal mapping zone (default server policy).
`tile_id`int (1..600)OptionalCoarse tile ID (default server policy).
Note
No GPS coordinates are required or expected. Spatial context is expressed as SWT + Tile.

Example response

{
  "convention_id": "<TIMEVERSE_CONVENTION_ID>",
  "R": 86400,

  "day_index": 1240,
  "dcal": { "cycle": 0, "year": 4, "month": 6, "week": 1, "day": 6 },

  "swt_zone": 6,
  "tile_id": 266,

  "hs_canonical_swt12": 2,
  "hs_local": 2,

  "phi_ticks": 59318,
  "phase_day_ppm_u32": 686550,

  "utc_iso_display": "2026-02-15T12:00:00Z",
  "stamp_display": "earth.1240.SWT6.266...."
}

Field classification

Verified semantics: `convention_id`, `R`, `day_index`, `dcal.*`, `swt_zone`, `tile_id`, `hs_*`, `phi_ticks`, `phase_day_ppm_u32`

Display-only: `utc_iso_display`, `stamp_display`

2) AI Phase Embedding (TPE)
Public

GET `/v1/ai/tpe-vector`

Convert tick-canonical phase into an embedding vector for AI models and agent alignment.

Query parameters

ParameterTypeRequiredDescription
`day_index`intOptionalDefaults to current.
`phi_ticks`intOptionalDefaults to current.
`mode`stringOptionale.g. `fourier_k4`, `fourier_k16`.

Example response

{
  "convention_id": "<TIMEVERSE_CONVENTION_ID>",
  "R": 86400,
  "day_index": 1240,
  "phi_ticks": 59318,

  "tpe_schema": "TV-TPE-2026-01",
  "mode": "fourier_k4",

  "tpe_vector_display": [0.89, -0.45, 0.12, 0.07, -0.33, 0.91, -0.10, 0.02],
  "context_window_display": "RECHARGE",
  "safety_gate_display": "OPEN"
}

Field classification

Verified semantics: `convention_id`, `R`, `day_index`, `phi_ticks`, `tpe_schema`, `mode`

Display-only: `tpe_vector_display`, `context_window_display`, `safety_gate_display`

Paid endpoints (overview)
Paid

These endpoints require an API key / pilot and are documented in the Enterprise page:

  • Quantum window decision: `GET /v1/quantum/decision`
  • Signed audit receipts (TSAE): `POST /v1/security/tsae`
  • Clockchain anchoring + merkle proofs
Need production access?
Request a demo or pilot access to unlock managed scheduling, signing, and anchoring.

SDK mapping (Public)

SDK methodEndpointNotes
`timeverse.getState()``GET /v1/core/state`Returns tick/HS/D-Calendar context.
`timeverse.getTpeVector(params)``GET /v1/ai/tpe-vector`Display-only floats, not for verification.