--api-first--transactional--headless

The Transaction Layer
for Agent Scheduling

Floyd is headless scheduling infrastructure for AI agents. Turn availability into reservable inventory with slot holds, deterministic policies, and timezone safety—built for the agent economy.

1

Define resources

Create staff, rooms, or equipment pools directly in Floyd to manage your time inventory.

2

Search valid slots

Request availability via API. Floyd applies your business hours and buffers to find valid windows.

3

Hold the slot

Create a short-lived atomic hold (2–10 mins) to lock the time while your agent negotiates the details.

4

Confirm transactionally

Commit the booking with idempotency keys. Floyd records the state and triggers your webhooks.

Primitives for Reliable Agent Scheduling

Atomic slot ledger

Calendar APIs aren't transactional. Floyd adds a ledger of holds to prevent double-booking.

Deterministic logic

Offload complex math to Floyd. Enforce buffers and lead times outside of your model prompts.

Retry-safe infrastructure

Networks fail. Use idempotency keys to ensure retried requests never create duplicates.

Framework friendly

Built for the ecosystem. Drop-in support for Vapi, Retell, and any tool-calling AI agent.

Native inventory

Manage resources directly in Floyd. Ideal for headless assets, staff, or shared equipment pools.

Webhook reliability

Trigger downstream workflows instantly with reliable webhooks for every confirmed booking.

Ready to build?Make scheduling reliable

Stop stitching together calendar APIs. Use holds, policies, and confirmations that behave correctly under concurrency.