About Floyd
Making Time
Programmable
for Agents.
The Problem
AI agents are booking appointments, reserving resources, and managing schedules. But they need more than calendar APIs. They need transactional guarantees.
Traditional calendar systems were designed for human interactions, not autonomous agents operating at scale. They can't handle concurrent booking requests, lack atomic reservation logic, and provide no safety for retries. The result? Double-bookings, race conditions, and complex state management in your application code.
Floyd provides booking infrastructure with the guarantees agents need: temporary holds with automatic expiry, database-level conflict prevention, and idempotent operations. When two agents compete for the same slot, the system handles it deterministically. One succeeds, the other receives a clear conflict response.
What we believe
01
Transactional correctness
Booking is not a CRUD operation. It requires atomic holds, conflict detection, and deterministic outcomes. Floyd treats every reservation as a database transaction.
02
Built for agents, not humans
Agents operate concurrently, retry aggressively, and don't read error messages. Every API surface is designed for machine clients first.
03
Open infrastructure
The Floyd Engine is open-source under Apache 2.0. The booking layer should be auditable, forkable, and self-hostable by anyone.
Open source
Apache 2.0. No vendor lock-in.
The Floyd Engine is fully open-source. Inspect the code, run it on your own infrastructure, and contribute back. The hosted API is how we keep the lights on, but the core is yours to own.
Get in touch
Have questions?
Whether you're evaluating Floyd, want to discuss a custom deployment, or just want to talk about the problem space. We'd love to hear from you.
© 2026, Floyd LLC