Application-facing temporal governance for production timing stacks. Your timing stack delivers time. GAL-2 governs whether applications should consume it.
Developer quickstart
RapidAPI is the fastest way to test the upstream GAL-2 Time API. The full
GAL-2 Time Contract runs locally as a daemon and exposes application-facing
governance through http://127.0.0.1:9095/contract.
/contract for application-facing governance.
The current evaluator preview is RC5.8 / 1.2.0-rc.3 and includes
macOS and Linux Docker ARM64 evaluator downloads, API key activation, and IXOYE
advisory witness visibility.
Hosted quickstart · API key tester · macOS RC5.8 · Linux Docker ARM64 RC5.8 · IXOYE advisory witness
Subscribe or test through RapidAPI, then use the API key shown in your RapidAPI dashboard. RapidAPI handles billing, quota, and usage for subscriptions created there.
Open GAL-2 on RapidAPIDirect GAL-2 plans activate the local daemon and the full Time Contract path. Your application integrates with the local contract endpoint instead of committing raw time directly.
Free evaluator downloads
Install the local daemon, then activate it with a GAL-2 API key. The download is
free for evaluation. The upstream GAL-2 authority requires an API key before the local
/contract endpoint can serve a LIVE Time Contract.
RC5.8 is the active public evaluator preview / enterprise pilot candidate. The macOS artifact is a customer-installable package with IXOYE live observer support and verifier fix. The Linux Docker ARM64 evaluator bundle is GPG signed, includes real API LIVE witness evidence, and has corrected internal SHA256SUMS. The canonical public Linux filename is retained for compatibility and resolves to the corrected payload.
WARMING,
reason=warming_no_cache, and safe_to_consume=false.
RapidAPI request
In RapidAPI, copy the endpoint and headers shown in your RapidAPI dashboard. The example below uses the RapidAPI key header. Keep the host and URL exactly as RapidAPI provides them for your subscription.
curl -s \
-H “x-rapidapi-key: YOUR_RAPIDAPI_KEY”
-H “x-rapidapi-host: gal-2-tm-time-api1.p.rapidapi.com”
https://gal-2-tm-time-api1.p.rapidapi.com/time
If RapidAPI shows a different base URL or host for your account, use the values from RapidAPI.
Example response shape
The response confirms that the request reached the GAL-2 time service. Field names may vary between RapidAPI, direct API access, and the full Time Contract daemon, but the goal is the same: evaluate governed time instead of blindly trusting raw local time.
{
“gal2_time”: “2026-05-27T17:34:38.399767Z”,
“utc_time”: “2026-05-27T17:34:38.404894Z”,
“drift”: {
“base_ms”: -7.83,
“wobble_ms”: 4.134,
“live_ms”: -5.127
},
“fractal_factor”: 3.761473,
“source”: “fractal+secret(hmac)+ema”
}
The upstream API response includes governed time plus engine metadata. These fields expose
API behavior and runtime conditions, but they are not a metrological UTC certification claim.
The full local Time Contract adds application-facing fields such as
safe_to_consume, mode, reason,
valid_until, monotonic_sequence, and
source_lineage.
SDK examples
fetch("https://gal-2-tm-time-api1.p.rapidapi.com/time", {
headers: {
“x-rapidapi-key”: “YOUR_RAPIDAPI_KEY”,
“x-rapidapi-host”: “gal-2-tm-time-api1.p.rapidapi.com”
}
})
.then((r) => r.json())
.then(console.log);
Python
import requests
headers = {
“x-rapidapi-key”: “YOUR_RAPIDAPI_KEY”,
“x-rapidapi-host”: “gal-2-tm-time-api1.p.rapidapi.com”,
}
response = requests.get(
“https://gal-2-tm-time-api1.p.rapidapi.com/time”,
headers=headers,
timeout=10,
)
print(response.json())
Full product path
Move from API testing to the Time Contract.
RapidAPI is useful for a first API test. Production-style integration should evaluate
the GAL-2 Time Contract locally, where the daemon exposes a governed contract before
your application commits time-dependent state.
curl -s http://127.0.0.1:9095/contract | python3 -m json.tool
curl -s http://127.0.0.1:9095/witness | python3 -m json.tool