Hotel API
Self-serve StandardSell hotels through your agent or application.
AI agents and conventional server applications use the same REST API to search current inventory, compare Brek with returned Expedia.com or Booking.com public rates, and complete a Brek booking. Register, accept the current approved terms, and create a Live application and API key. Standard Live is self-serve—no sales call or manual activation required. Test keys are optional for sandbox testing.
Start with your question
- Can a regular application use this API?
- Yes. AI agents and conventional server applications use the same Bearer key, REST endpoints, and OpenAPI contract. MCP is optional and read-only.
- How do I get an API key?
- Register in Brek Partner Console, accept the current approved terms, then create a Live application and key. Store the one-time secret server-side; verify the application with capabilities. Test is optional.
- Does Test search current hotel inventory?
- Yes. Test searches current inventory and uses Stripe test mode, while supplier booking, confirmation email, and cancellation stay simulated.
- When do I need Enterprise?
- Only for higher limits, negotiated commercial terms, custom launch requirements, or dedicated support. Standard starts without a sales call.
Standard plan
Build first. Talk to sales only when you need Enterprise.
Create a Partner Console account, accept the current approved terms, and issue a Live application key. Start searching immediately, then use Hosted checkout to let the traveler pay securely on Brek. No invitation, sales call, credit line, or receiving bank account is required for Standard Live access. Payment and booking still require runtime readiness and explicit traveler approval. Commission receiving details and manual settlement are a separate process.
Read the Standard program terms- Revenue share
- 10% of profit
- Request limit
- 60/min/app
Choose REST or MCP
These are the current integration surfaces. Use REST/OpenAPI for transactions and the existing MCP only for read-only discovery. REST and MCP identifiers are not interchangeable.
Choose the page for your job
Quickstart
The complete path from sign-up and API key creation through search, room selection, quote, checkout, and booking care.
Start building →
API Reference
Exact methods, paths, headers, request fields, responses, and safety rules for every endpoint.
Look up an endpoint →
Agent entry
A machine-readable map that lets an AI agent find onboarding, policy, and endpoint contracts.
Open agent-commerce.md →
Action: redirect or resolve, then redirect
Show the price and open the provider
Expedia.com and Booking.com public prices may appear when Brek has a safe HTTPS comparison; neither provider is guaranteed for a search. Search presents Expedia before Booking, then orders results from the same provider by its reported total. That order is a display priority, not proof that prices are like-for-like. Follow the typed action: some prices already carry a redirect; others require one authenticated read-only provider recheck first. The external provider owns payment, confirmation, changes, cancellation, taxes, fees, room terms, and final price recheck.
No Agent rev share in v1
Brek transaction lane
Recheck the room and book with Brek
Load all room offers, quote the traveler's selection, then use hosted or native checkout. Brek owns the reservation lifecycle and traveler confirmation.
Eligible for realized-profit share
One request
Search the comparison and booking lanes together
The API key selects the partner agreement and the server-side Brek inventory connections. Search returns the left public-comparison lane and the right, unmasked Brek-bookable offer after Brek's applicable final pricing. Agents never send another markup or choose a more favorable connection.
curl https://api.brek.com/api/v1/agent-commerce/search
-H "Authorization: Bearer $BREK_AGENT_API_KEY"
-H "Content-Type: application/json"
-d '{
"geo": { "lat": 47.6062, "lng": -122.3321, "radiusKm": 12 },
"checkIn": "<future check-in: YYYY-MM-DD>",
"checkOut": "<future check-out: YYYY-MM-DD>",
"occupancies": [{ "paxes": [{ "age": 34 }] }],
"currency": "USD"
}'Built for agents and applications
The same hotel layer for every kind of product
Travel assistants
Turn a traveler conversation into comparable choices and a confirmed reservation.
Enterprise agents
Keep policy, payment authorization, booking status, and cancellation explicit.
Travel applications
Use ordinary server-side REST and OpenAPI with separate keys, environments, and commission reporting.
Building blocks
Agents
Give travel assistants and enterprise agents the tools to search, compare, sell, and service hotels.
Understand the model
API Reference
Look up the exact request, response, headers, fields, and safety contract for every Brek Hotel API endpoint.
Look up an endpoint
MCP
Add authless hotel discovery and rate comparison to compatible assistants without enabling transactions.
Connect the MCP server
Checkout
Use Brek-hosted checkout when the agent cannot pay, or native checkout when it can complete authorization.
Choose a checkout path
Designed to fail clearly
Price changed
A fresh quote requires explicit traveler reconfirmation. The API never silently accepts a higher amount.
Not comparable
If currencies or total-price bases differ, the response tells the agent not to make a savings claim.
External checkout
Redirect rates never appear as Brek bookings and never enter the v1 partner commission ledger.