One API to book, cancel, and modify restaurant reservations. Built-in idempotency, policy enforcement, and audit trails. MCP-compatible out of the box.
Today's AI agents can plan multi-step tasks, but executing real-world actions like restaurant reservations is fragile. Duplicate bookings, lost cancellations, and missing audit trails are common failure modes.
AgentReserve provides the transaction infrastructure layer that makes agent-driven reservations reliable, auditable, and safe.
Your agent decides to book a table for a customer.
POST /api/v1/agent/restaurant/book with idempotency key.
Spending limits, rate limits, and approval workflows evaluated.
Reservation created through the restaurant provider.
Transaction confirmed, audit logged, response cached.
Three endpoints. JSON in, JSON out. Every request is validated with Zod, every response follows a consistent schema.
/api/v1/agent/restaurant/book/api/v1/agent/restaurant/cancel/api/v1/agent/restaurant/modify{
"restaurantName": "Golden Gate Grill",
"city": "San Francisco",
"partySize": 4,
"datetime": "2026-03-20T19:00:00Z",
"customer": {
"name": "Jane Doe",
"email": "jane@example.com"
}
}{
"mcpServers": {
"agentreserve": {
"url": "https://your-host/api/v1/mcp",
"headers": {
"Authorization": "Bearer ar_live_..."
}
}
}
}Expose restaurant booking tools directly to Claude, GPT, or any MCP-compatible agent framework. Three tools available out of the box:
book_reservation -- Create a new bookingcancel_reservation -- Cancel an existing bookingmodify_reservation -- Modify time or party sizeEvery request is safely retryable. Duplicate bookings are impossible with the Idempotency-Key header. Responses are cached and replayed automatically.
Define spending limits, rate limits, time restrictions, and approval workflows. Policies are evaluated server-side before any reservation executes.
Every booking, cancellation, modification, and policy decision is recorded with timestamps, actor identity, and full context. Immutable and queryable.
State-machine-backed transactions track every reservation from pending through confirmed, modified, or cancelled. No orphaned bookings.
Every resource -- restaurants, reservations, API keys, policies -- is scoped to a single organization. Full multi-tenant isolation.
Keys are hashed with SHA-256 before storage. Raw keys are shown once at creation. Connector tokens are encrypted with AES-256-GCM.
Create an account, generate an API key, and make your first restaurant reservation. No credit card required.