Rentals API for any rental platform: gear, cameras, bikes, tools, venues

ChefSphere rentals APIs are built for product teams shipping a rental platform of any kind: cameras and production gear, bikes and outdoor equipment, power tools, event venues, vehicles, fashion, or peer-to-peer inventory you already own. Availability calendars, deposits, owner approval, and renter handoff are the product spine—not a grocery or cookware assumption.

This guide focuses on rental intent: listing rentable inventory, blocking dates, requesting and deciding bookings, and closing out an ongoing rental. It is not the multi-seller marketplace checkout guide and not a food-vertical playbook. Pair rentals with seller KYC and wallets when money and trust matter; pair with media when photos sell the listing.

Inventory needs clear ownership, categories, and media so renters can decide without inventing schema mid-sprint. Availability needs calendar semantics that prevent double-booking when two requests race. Deposits and damage policies need status paths your support team can explain. Owner approve/decline and renter cancel flows need deterministic outcomes clients can render.

Reads for browsing inventory stay lighter on the prepaid ledger; writes that reserve dates, move deposits, or end a rental sit heavier because they mutate scarce inventory state. That is intentional. Unused tokens stay on one balance shared with marketplace, live, AI, and the rest of the nineteen modules.

During early access you request access, we review what you are building, and we contact you when keys and onboarding open for your markets and rental model. Docs today include illustrative OpenAPI shapes for planning; production contracts follow once early access is granted.

Authentication is Firebase-style: an X-API-Key on each call, billed against your prepaid token balance. Starter packs begin at $29 for 200,000 tokens; Growth and Scale raise volume across the public band. One balance spends across rentals and every other module without a separate meter.

Plan capacity around browse-heavy discovery versus booking spikes during weekends or events. If your first release is inventory browse with sparse bookings, Starter may be enough to integrate. If you expect concurrent booking plus KYC or media transforms, Growth or Scale is the honest planning band.

Choose rentals when time-bounded use of an asset is the product: calendars, deposits, owner/renter roles, and return handoff. Choose marketplace when buyers purchase goods with cart, checkout, returns, and seller payouts as the primary journey. Many products use both—sell accessories on marketplace, rent scarce gear on rentals—on the same prepaid balance.

Request early access with a short note on categories, geography, peer versus fleet inventory, and whether deposits or KYC gate the first booking. Related reading covers marketplace, seller KYC, and wallet currency so money and trust are designed early.