/vendor/agoda/AgentRouting.json or
/vendor/agoda/AgentContext.json directly.
agoda.com
Overview
Does agoda.com support MCP?
No confirmed MCP support was found for agoda.com as of 2026-06-23.
What agentic protocols does agoda.com support?
As of 2026-06-23, agoda.com has confirmed support for proprietary.
Is agoda.com's API publicly accessible or partner-gated?
Partner only.
Does agoda.com explicitly prohibit automated access?
Yes. agoda.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is agoda.com agent-ready?
Partial. agoda.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No vendor-specific evidence located that Agoda exposes, consumes, or has joined the Agent2Agent (A2A) protocol. The A2A launch partner ecosystem publicly named includes companies such as Atlassian, Salesforce, SAP, MongoDB, LangChain, and PayPal; Agoda is not among the publicly named partners. Agoda's own recent AI-related announcements (an open-source API agent that bridges MCP clients to GraphQL/REST, and an AI Developer Report) reference MCP but make no reference to A2A or the merged-in Agent Communication Protocol. Recorded as not_found rather than confirmed_absent because no Agoda-issued statement explicitly rules A2A out.
OpenAI/Stripe's Agentic Commerce Protocol (commerce/checkout standard) launched Sept 2025 with retail merchants (e.g., Etsy, Shopify sellers); OpenAI scaled back Instant Checkout in early 2026 to a narrower pool of large integrated retailers and to date no OTA/travel partners — including Agoda — have been publicly named as ACP merchants. No Agoda-issued statement adopting or rejecting ACP was located, so recorded as not_found rather than confirmed_absent.
AP2 was announced September 2025 by Google with 60+ launch partners spanning card networks, PSPs, wallets, and merchants (e.g. Mastercard, American Express, PayPal, Adyen, Coinbase, Salesforce, Etsy, Intuit, Revolut, Worldpay, Ant International, JCB); Agoda is not listed among them in any source reviewed. No vendor-issued statement from Agoda about AP2 adoption or rejection was located, so recorded as not_found rather than confirmed_absent. Passive checks (HTTPS, domain alignment, doc quality) were not applicable because no Agoda-specific AP2 surface exists to inspect, hence insufficient_data on sketchiness.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No vendor-specific evidence of Agoda implementing the Stripe/Tempo Machine Payments Protocol was located. MPP coverage names Stripe and Tempo as co-authors with Visa as a design partner; Agoda is not mentioned among launch participants, and Agoda's partner-facing payment documentation describes traditional card/POS/bank-transfer payout flows with no reference to MPP, x402, or agentic settlement rails. Recorded as not_found rather than confirmed_absent because no Agoda statement explicitly rejecting or deprecating MPP was found.
NLWeb was announced by Microsoft at Build 2025 with a named cohort of initial publishing/ecosystem collaborators including Tripadvisor, Shopify, Eventbrite, Hearst (Delish), O'Reilly Media, Chicago Public Media, Common Sense Media, Allrecipes/Serious Eats (DDM), Snowflake, Qdrant, Milvus, and Inception Labs; Agoda is not among them and no /ask or /mcp endpoint on agoda.com or a vendor statement of NLWeb adoption was located. Recorded as not_found rather than confirmed_absent because no Agoda-specific statement (e.g. a public decision to skip NLWeb) was located — only the absence of Agoda from the third-party launch-partner roster, which per rule 2 is not evidence about this vendor's own posture. Sketchiness left at insufficient_data because no Agoda-hosted NLWeb surface could be passively inspected.
Search across Google/Shopify UCP announcements, the UCP spec site (ucp.dev), the UCP GitHub org, and travel-press coverage of the lodging expansion shows named hotel/travel launch partners as Booking.com, Expedia Group, Accor, Amadeus, Choice Hotels, Hilton, IHG, and other retail co-developers (Shopify, Etsy, Wayfair, Target, Walmart); Agoda is not listed among UCP partners, adopters, or co-developers in any source located. No Agoda-published statement on UCP was found, so this is recorded as not_found rather than confirmed_absent. Passive checks (HTTPS, domain alignment, docs quality) were not applicable since no Agoda UCP surface exists to inspect, hence insufficient_data on sketchiness.
No vendor-published evidence located indicating agoda.com exposes in-page agent-callable tools via a browser-layer protocol. WebMCP itself is an early/emerging proposal with limited adopters; no Agoda mention found in WebMCP discussion threads, repos, or Agoda's own developer/partner pages. Recorded as not_found rather than confirmed_absent because no Agoda-specific statement (e.g. an explicit denial or deprecation notice) was located.
No evidence located that Agoda accepts, settles, or exposes any endpoint priced via the x402 HTTP-402 stablecoin payment protocol. Public x402 ecosystem references name Coinbase, Cloudflare, Google, Vercel, AWS CloudFront/WAF, Stripe, Stellar, and Solana as supporters or facilitators; Agoda is not among any named participant, partner, or merchant list found. Recorded as not_found rather than confirmed_absent because no Agoda-specific statement (deprecation, refusal, or non-support notice) was located — only an absence from third-party partner lists, which per rule 2 is not vendor-specific evidence.
OpenAI's October 2025 Apps SDK launch named pilot partners Booking.com, Canva, Coursera, Figma, Expedia, Spotify, and Zillow; Agoda is not among them. Subsequent searches surfaced no Agoda-specific announcement, developer docs, or ChatGPT app listing referencing the Apps SDK. Recorded as not_found rather than confirmed_absent because no Agoda statement explicitly disclaiming an Apps SDK build was located.
Affiliate/consumer-side hotel distribution: property content retrieval, search/availability and pricing lookup, booking creation, and post-booking management (cancellation, retrieval) via the Affiliate Long Tail / Content / Search / Book / Post-book endpoints exposed through the Agoda Developer Portal.
Vendor-documented HTTP/JSON affiliate distribution API surface with named sub-APIs (Content, Search, Book, Post-book, NHA, Affiliate Lite). Documentation is on the vendor's own domain (partners.agoda.com) over HTTPS; access requires approval into the affiliate program rather than self-serve key issuance, hence partner_only.
Supply-side / property-management interface for accommodation providers and channel managers: pushing and updating property content, availability, rates and inventory (ARI), reservation retrieval, and onboarding new properties programmatically — i.e. the channel-manager/connectivity counterpart to the YCS extranet UI.
Distinct from the affiliate/distribution API: this is the supplier-facing Connectivity / Content Push / Onboarding / ARI surface documented at developer.agoda.com/supply and agodaconnectivity.com, used by channel managers and direct-integrated properties. Access is gated to vetted connectivity partners (request to agoda.chain.support@agoda.com), not generally callable.
Sandbox lacks outbound network access (curl returned HTTP 000 for all probed paths), so passive checks of llms.txt, AGENTS.md, /.well-known/agent, /.well-known/ai-plugin.json, and agents.json on agoda.com and www.agoda.com could not actually be performed. Per discipline rule that a structurally-blocked check is unable_to_verify rather than not_found, recorded as such; no vendor-specific evidence either way was obtained.
Summary
Has agent interface: partial
Apply to the Agoda Affiliate Program via partners.agoda.com to obtain credentials for the affiliate distribution API (Content, Search, Book, Post-book) for consumer-side hotel discovery and booking; channel managers and direct-connect properties should instead request supply-side connectivity access via agoda.chain.support@agoda.com for the developer.agoda.com/supply surface. Do not scrape agoda.com — automated access is explicitly forbidden by the site's Terms of Use.
AgentContext
Verified discrepancies
Vendor claim: Agoda advertises hotel room prices at search and listing stages, presenting these as the deal price the customer will pay. The platform's own marketing implies the displayed rate reflects the total cost of the booking.
What actually happens: Independent consumer reports and a 2019 regulatory finding by the UK Competition and Markets Authority (CMA) documented that Agoda listed prices that excluded applicable taxes and fees at the search stage, causing the price shown at checkout to be materially higher than the initial advertised price. This gap was specifically flagged as making Agoda's displayed discounts appear more favorable than those of competitors who did include full fees in their listed prices. Multiple ongoing consumer complaints describe checkout totals that are unexpectedly higher than the initially displayed rate, with taxes and surcharges not clearly itemized upfront.
Agent guidance: An agent completing a hotel booking on Agoda must not treat the price shown on the search results or property listing page as the final transaction amount. Before confirming any booking, the agent must navigate fully to the checkout/payment page and capture the fully-loaded price including all taxes, fees, and surcharges. If the checkout total differs from the initially displayed price, the agent should surface this difference to the user before proceeding with payment, rather than automatically completing the booking at the higher undisclosed amount.
- The UK Competition and Markets Authority's 2019 investigation into hotel booking sites found that Agoda listed prices excluding taxes and fees, making advertised discounts appear larger than they actually were, and required corrective action.
- Widely documented consumer reports describe Agoda showing a lower initial price that rises significantly at checkout due to taxes and fees not clearly itemized upfront, causing confusion and frustration for users.
Vendor claim: Agoda displays specific room types (e.g., riverfront rooms, specific categories) and nightly rates on its booking pages, implying these are the confirmed rooms and prices the user will receive upon completing a transaction.
What actually happens: Multiple independently documented complaints show that: (1) rooms displayed and paid for on Agoda are not the rooms provided at the property (guests receive lower-category rooms than booked); (2) prices displayed at search/listing stage differ materially from the amount ultimately charged at checkout (price increases of ~THB 200 and similar unexplained increments documented); and (3) bookings confirmed by Agoda with payment taken show no corresponding reservation at the hotel, with Agoda falsely marking guests as no-shows rather than acknowledging ghost inventory.
Agent guidance: An agent booking on Agoda should not treat a booking confirmation and payment receipt as proof of a valid reservation. Before completing a transaction, the agent should: (1) capture a screenshot of the displayed room type and rate before checkout; (2) after booking, independently contact the hotel directly to verify the reservation exists under the correct room category; and (3) flag any checkout price that differs from the displayed listing price to the user before finalizing payment, as undisclosed incremental charges have been documented at the payment step.
- TravelUpdate buyer-beware article documents a specific complaint where a guest paid a premium for a riverfront room through Agoda but was given the cheapest available room upon arrival, with no refund issued — a textbook bait-and-switch on room type.
- Trustpilot reviews for Agoda explicitly cite a bait-and-switch on final price: the price shown at booking time was lower than the price actually charged, with an unexplained difference of approximately THB 200.
- Trustindex review (January 2025) documents a confirmed booking with payment debited where no reservation existed at the hotel on arrival; Agoda's response falsely recorded the guest as a no-show, consistent with ghost inventory being sold.
Vendor claim: Agoda's Terms of Service state that all transactions and disputes are governed by the laws of Singapore and that Agoda acts as an intermediary or agent, with liability and legal counterparty identity varying by booking model (pay-now vs. pay-at-hotel). Agoda implies it is the single point of contact for payment and refunds on prepaid bookings.
What actually happens: Independent evidence — including a 2024 Israeli Supreme Court ruling in a class-action against Agoda — confirms that Agoda's claim of Singapore-law exclusivity and its framing of its own liability role can be legally invalid in consumer jurisdictions. In the pay-now (merchant/prepaid) model, Agoda collects payment and is the merchant of record, but in practice routes refund disputes to hotels or partner affiliates, creating a situation where no party straightforwardly accepts liability. Consumer complaints document Agoda deflecting refund responsibility to the hotel even on prepaid bookings where Agoda held the funds.
Agent guidance: Before completing a booking on Agoda, an agent should check the booking confirmation to determine which model applies (pay-now vs. pay-at-hotel), because the merchant of record and the party responsible for refunds differs between the two. For pay-now bookings, the agent should record Agoda as the payment counterparty but be aware that Agoda may redirect refund disputes to the property. If a refund or dispute is anticipated, the agent should note that Agoda's Singapore-law terms may not be enforceable as the sole governing framework in the user's jurisdiction, and should escalate via the user's card issuer chargeback route rather than relying solely on Agoda's internal process.
- The Israeli Supreme Court (May 27, 2024) ruled in Agoda Company Pte. Ltd v. Shay Tzvia that Agoda's Singapore choice-of-law clause did not shield it from Israeli consumer protection law, confirming that Agoda's stated legal identity and governing terms can be overridden in consumer jurisdictions — directly affecting who the legal counterparty is.
- A Philippine legal commentary explains that Agoda operates under two distinct models — agency (pay-at-hotel, hotel is merchant of record) and merchant/prepaid (Agoda is merchant of record) — but consumers are not clearly informed which model applies to their specific booking at the time of transaction, creating ambiguity about who holds liability for a refund.
Vendor claim: Agoda displays 'Free Cancellation' or 'Risk-free booking — cancel without any charge before [date]' labels on eligible listings at the point of purchase, indicating that customers who cancel within the stated window will receive a full refund.
What actually happens: Multiple documented consumer complaints from 2024–2025 show Agoda denying refunds to customers who cancelled within the advertised free-cancellation window, charging cards ahead of the stated payment date, or deflecting responsibility onto hotels rather than honoring the policy shown during booking. In at least one case a customer received a cancellation confirmation yet was still told no refund would be issued.
Agent guidance: Before completing any Agoda booking that shows 'Free Cancellation', an agent should capture a screenshot or full-page record of the cancellation terms displayed at checkout (including the exact cut-off date and any payment schedule). If a cancellation is later needed, the agent should initiate the request well within the displayed window AND retain the Agoda cancellation confirmation email, as enforcement has been inconsistent. If a refund is denied despite in-window cancellation, the agent should escalate via a formal written dispute referencing the booking-screen policy text, and if unresolved, advise the user to pursue a chargeback with their card issuer or file a complaint with the relevant consumer authority.
- A 2025 consumer complaint documents a customer who cancelled before the explicitly stated 'free cancellation until May 8, 2025' deadline but was told by Agoda that no refund would be issued, with Agoda citing 'accepted terms and conditions' as justification.
- Multiple 2024–2025 complaints on a consumer dispute platform describe Agoda charging cards immediately after payment details were updated despite a stated 'no payment required until' future date, and refusing refunds after customers cancel within the allowed window.
- A complaint thread documents a customer who selected a room with no on-screen indication of non-refundability; Agoda denied responsibility, claiming it was the hotel's policy, while the hotel denied receiving the payment — illustrating a gap between policy presentation and enforcement.
Vendor claim: Agoda presents itself as a fully functional booking platform where confirmed reservations are reliably transmitted to hotels and accurately reflect the selected dates, room types, and pricing — implying that a completed booking flow results in a valid, honored reservation.
What actually happens: Documented evidence from Japan's Tourism Agency and multiple hotel operators shows that bookings confirmed through Agoda's platform frequently fail to transmit correctly to hotels, arrive with wrong dates or room details, or include price discrepancies — rendering the completed transaction effectively void or incorrect without any upfront disclosure of this systemic risk. Several major hotel chains publicly warned guests not to use Agoda, and Japan's Tourism Agency issued a formal business improvement order (gyomu kaizen meirei) against Agoda International Japan after the problems persisted following Agoda's own pledges to fix them.
Agent guidance: When completing a hotel booking through Agoda — especially for properties in Japan or with Agoda International Japan — the agent should not treat a booking confirmation screen as sufficient proof of a valid reservation. The agent must retrieve and record the Agoda booking confirmation number, then independently verify with the hotel directly (by phone or email) that the reservation appears in their system with correct dates, room type, and rate before informing the user the transaction is complete.
- Hospitality Today reports the Japan Tourism Agency formally warned Agoda International Japan over persistent booking failures including missing reservations, incorrect booking details, and price discrepancies, with penalties threatened if improvements were not made.
- A detailed secondary account confirms Agoda received a formal 'business improvement order' from Japan's Tourism Agency after hotel chains including Hoshino Resorts and Toyoko Inn publicly warned travelers that Agoda bookings were not reliably honored at their properties.
Human handoff required for
Stop and surface the price difference to the user before proceeding when the fully-loaded checkout total (including all taxes, fees, and surcharges) is materially higher than the price shown on the search results or property listing page — do not auto-complete the booking at the undisclosed higher amount.
Stop and alert the user when the room type or rate visible at checkout differs from what was displayed on the listing page, specifically when an unexplained incremental charge (e.g., a per-night or per-booking surcharge not shown at listing stage) appears without itemized disclosure before payment is captured.
Stop and escalate to a human when, after a booking confirmation and payment receipt have been issued by Agoda, the hotel directly reports that no corresponding reservation exists in their system — do not treat the Agoda confirmation number alone as proof of a valid reservation, particularly for properties in Japan or those publicly flagged as having Agoda transmission issues.
- Japan's Tourism Agency issued a formal business improvement order (gyomu kaizen meirei) against Agoda International Japan in 2024 after persistent reports from hotel operators of bookings that were missing, contained incorrect dates or room details, or reflected price discrepancies not disclosed during the booking flow.
- Multiple independently sourced complaints document confirmed-paid Agoda bookings that carried no hotel-side reservation, with Agoda falsely marking affected guests as no-shows rather than acknowledging the transmission failure.
Stop and escalate to a human when the user wants to cancel a booking that Agoda displayed as 'Free Cancellation' but Agoda denies the refund, charges the card ahead of the stated payment date, or deflects responsibility to the hotel — at that point the agent should advise the user to pursue a card-issuer chargeback and file a complaint with the relevant consumer authority rather than continuing to engage only Agoda's internal process.
Stop and escalate to a human when a refund or dispute arises on a prepaid (pay-now) Agoda booking and Agoda redirects responsibility to the hotel rather than processing the refund directly — the agent cannot resolve this through Agoda's platform alone because the enforceable merchant of record is ambiguous and Agoda's Singapore-law terms may not be the sole governing framework in the user's jurisdiction.
- A May 2024 Israeli Supreme Court ruling confirmed that Agoda's choice-of-law clause and implied legal identity can be overridden in consumer jurisdictions, and legal commentary documents that Agoda operates under two models (agency vs. prepaid/merchant) without consistently disclosing which applies at booking time.
- Consumer complaints document Agoda deflecting refund responsibility to the hotel even on prepaid bookings where Agoda held the funds, leaving no party straightforwardly accepting liability for the disputed amount.
Stop and escalate to a human when the booked room type confirmed by Agoda does not match the room category assigned by the hotel at check-in (e.g., a lower-tier room substituted for a booked riverfront or premium category) — the agent should not accept the hotel's substitution as equivalent and should document the originally booked specification before the user departs.
Five discrepancy categories were checked for agoda.com: (1) Pricing — scans found documented evidence of checkout prices materially exceeding search-stage displayed prices, supported by a 2019 UK CMA regulatory finding and ongoing consumer complaints; (2) Availability — scans found documented evidence of ghost inventory, room-type misrepresentation, and checkout price inflation, sourced from TravelUpdate, Trustpilot, and Trustindex complaints through 2025; (3) Identity — scans found documented evidence of merchant-of-record ambiguity and liability deflection, supported by a May 2024 Israeli Supreme Court ruling and legal commentary on Agoda's dual booking models; (4) Policy — scans found a consistent pattern of 'Free Cancellation' terms displayed at booking but not honored in practice, sourced from multiple consumer complaint platforms in 2024–2025; (5) Undisclosed constraints — scans found a formal business improvement order issued by Japan's Tourism Agency against Agoda International Japan in 2024, corroborated by hotel-operator reports of missing or incorrect booking transmissions. All five categories returned findings with identified sources; no category scans were blocked or returned null results, though the depth of primary regulatory documentation varied by category.