Create resources
Add staff, rooms, or any bookable asset. Each resource has its own allocation timeline.
Hold the slot
Your agent creates a hold on a time range. Floyd locks the resource and starts the TTL countdown.
Deterministic outcomes
Every request gets an explicit response. Success, overlap_conflict, or hold_expired. No ambiguity.
Confirm or expire
Confirm the allocation to finalize, or let the hold expire. Every decision is recorded for audit.
See it in action
Two agents try to book the same slot. One wins, one gets a clear conflict response.
POST /v1/ledgers/:id/allocations
{
"resourceId": "dr-smith",
"startAt": "2026-01-08T10:00:00Z",
"endAt": "2026-01-08T11:00:00Z"
}{ "status": "hold" }POST /v1/ledgers/:id/allocations
{
"resourceId": "dr-smith",
"startAt": "2026-01-08T10:00:00Z",
"endAt": "2026-01-08T11:00:00Z"
}{ "error": "overlap_conflict" }No race conditions. No double-booking. The 409 is the feature.
The Booking Layer for Agent Workflows
Atomic slot holds
Lock a time slot while your agent negotiates. The hold is atomic and expires if not confirmed.
Concurrency safe
Database constraints enforce correctness. Works reliably under parallel calls, retries, and high load.
Safe retries
Networks fail. Pass an idempotency key and retried requests return the same result, never duplicates.
Built for AI agents
Works with Vapi, Retell, Bland, and any tool-calling agent that needs reliable booking.
Resource management
Create staff, rooms, or equipment as bookable resources. Floyd tracks what is booked and when.
Request log for debugging
Every request is logged with outcome. Debug conflicts, trace failures, prove correctness.
