CalculationTime

Private beta API

CalculationTime API

A structured time, date, geospatial, solar and astronomy API is now running at api.calculationtime.com. Public proof endpoints are live, and protected calculation endpoints are available to approved beta testers with privately issued API keys.

Request beta accessOpenAPI contractLive status
public demo200 OK
GET /v1/time/utc

{
  "timezone": "UTC",
  "sla_claimed": false,
  "accuracy_model": {
    "statement": "Current UTC is read from the API host system clock. Public accuracy claims require external monitoring evidence."
  }
}
API hosthttps://api.calculationtime.com
RuntimeNode / Fastify behind nginx and TLS
Service version0.1.0
OpenAPI paths25 documented routes
Automated tests37 passing on Jack-side backend report
CORSCalculationTime origin allowed for public status proof
API keysPrivate beta keys issued by request
Key storageRaw keys shown once; stored as hashes

Public now

Live endpoints that can be shown today

GET/health

Service health and readiness flags

GET/v1/status

Public status and endpoint-family inventory

GET/v1/time/utc

Public UTC proof from the API host clock

GET/api/v1/utility/tagline

Public utility demo endpoint

GET/openapi.json

OpenAPI 3.1 contract draft

Key required

Protected calculation families

These private beta families are present in the API map and protected by API-key enforcement. Request beta access for protected endpoint trials, higher rate limits, commercial usage and pricing conversations. The next natural-calculation lane is astronomy and calendar events: time, place, sky, solar position, moon phases, seasons and eclipse data with explicit source attribution.

  • Time and timezone lookup
  • Date difference and date addition
  • Business days, jurisdictions and holidays
  • Geospatial distance, midpoint, bounding box and nearby lookup
  • Solar position
  • Astronomy ephemeris and natural-world calendar events
  • Monitoring canary

Natural calculation infrastructure

Astronomy API scope under backend proof

CalculationTime's private-beta API is expanding around cacheable natural-world calculations: time, date, location, solar position, moon phases, seasons and astronomy events. Astronomy features should name Astronomy Engine by Don Cross where it is used, respect the MIT license, and never imply upstream endorsement.

GET/v1/astronomy/seasons

Build order drafted. Equinox and solstice UTC timestamps for a requested year using Astronomy Engine.

GET/v1/astronomy/moon-phases

Next candidate. Upcoming new, first quarter, full and third quarter moon events after backend proof.

GET/v1/astronomy/eclipses

Observer logic pending. Global and local eclipse search require stricter visibility and comparison proof.

Integration model

One brand surface, one service surface

calculationtime.com

Product, trust and docs

Host the API landing page, use cases, examples, request-access path, pricing when approved, accuracy notes and developer guides on the main site where visitors already understand the CalculationTime brand.

api.calculationtime.com

Service and machine contract

Keep JSON endpoints, health, status, OpenAPI and minimal service docs on the API subdomain. It should stay operational, stable and easy for developers to test.

Trust posture

What we can safely say

The API is live, protected routes reject unauthenticated requests, public health/status/UTC/tagline routes respond, CORS is enabled for CalculationTime, and the OpenAPI contract exposes a serious route map across time, date, business-day, holiday, geospatial, solar and astronomy work.

API keys are issued privately for approved beta testers. Raw keys are shown once at provisioning, stored as hashes, and can be rotated or revoked by the backend operator without exposing real secrets in public docs.

Hold back

What should not be marketed yet

  • No public SLA claim yet
  • No instant self-serve signup yet
  • No billing or customer dashboard promise yet
  • No self-service key issuing yet
  • No automated key rotation UI yet
  • No developer analytics portal yet
  • No rate-limit headers or Retry-After claim yet
  • Protected browser examples must never include private keys