schedule-bit
Developer beta Read the API Get a key Coming soon

What’s live.

Everything here runs on the dev deployment and passes the smoke suite (verified 2026-09-26). What isn’t built yet says so.

R = read W = write Live = pushed as it happens LiveComing soon

Worlds

  • create a World (a resource) create a resource with a preset W Live
  • list / describe preset · seats · head hash R Live

Presets

  • temporal-hour (day → 24 h) positions by date R Live
  • temporal-minute (hour → 60 m) positions by date + hour R Live

Occupiers

  • holders · events · series who can hold, with rank/pinned R W Live
  • capacity (seats) N may hold one slot at once W Live

The door

  • claim receipt or refusal, never both W Live
  • claim:explain judge without writing R Live
  • soft hold (until …) intent that lapses by the clock W Live
  • confirm · give-up · queue firm up, let go, wait in line W Live
  • release · handover give back, pass on in one act W Live
  • displace (by rank) loser told, offered elsewhere W Live
  • sweep lapse overdue soft holds W Live

Reading

  • offered free slots at a position R Live
  • holdings held + soft slots of one party R Live
  • journal ?since= sealed commits, hash-chained R Live

Relays

  • take a hand in copy another World's busy-ness W Live
  • lay a relay (legs, gaps, after) one job, many hands, ordered W Live
  • windows every start where all legs fit R Live
  • ask · sync · withdraw · delegate the four acts on a relay W Live
  • standing + possible where it stands, what's next R Live

Asks (a hand's inbox)

  • list asks what planners want of you R Live
  • answer: accept / reject / takeBack / moveTo your yes, no, take-back, or counter-slot W Live

Events

  • watch (WebSocket) every commit, as it lands Live Live
  • webhooks (signed, retried) ask.received, ask.answered… W Live Live

Coming soon

  • Cross-organisation relays Today a relay's hands must be in the planner's workspace (phase 3). Coming soon
  • Self-serve sign-up, a dashboard or console (hosted Relay Studio), billing and plans (phase 3) Coming soon
  • A production hostname and an SLA Dev only, today. Coming soon
  • An official SDK package Use plain HTTP; the examples above are the reference. Coming soon
  • Presets beyond temporal-hour and temporal-minute The library has spatial and custom configurations; the API doesn't expose them yet. Coming soon
  • WebSocket authentication for browsers The watch needs an Authorization header, which browsers can't send on a WebSocket, so it's server-side only for now. Coming soon
  • Federation with other clouds, and data residency (phase 4) Coming soon
  • Idempotency keys expire after 24 h, and webhook secrets are stored in the directory as given (encryption at rest is planned) Coming soon