This is a human-readable page. If you're an agent, fetch /vendor/flipkart/AgentRouting.json or /vendor/flipkart/AgentContext.json directly.

flipkart.com

last checked 2026-06-30

Overview

Does flipkart.com support MCP?

No confirmed MCP support was found for flipkart.com as of 2026-06-30.

What agentic protocols does flipkart.com support?

As of 2026-06-30, flipkart.com has confirmed support for proprietary.

Is flipkart.com's API publicly accessible or partner-gated?

Partner only.

Does flipkart.com explicitly prohibit automated access?

Yes. flipkart.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.

Is flipkart.com agent-ready?

Partial. flipkart.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.

Protocols

A2A not found

Flipkart appears as an endorser of Google's Universal Commerce Protocol (UCP), which lists A2A as one of its supported transports alongside REST and MCP. However, endorsing UCP as a commerce standard is not the same as Flipkart implementing or exposing an A2A-compatible agent endpoint. The original A2A protocol launch (April 2025) named partners include Atlassian, PayPal, Salesforce, SAP, ServiceNow, and Workday — Flipkart is not among them and no vendor-specific A2A implementation evidence was found.

ACP not found

No evidence found linking Flipkart to the Agentic Commerce Protocol (OpenAI/Stripe). Official ACP launch partners named in OpenAI and Stripe announcements are Etsy and Shopify merchants (Glossier, Vuori, Spanx, SKIMS). Flipkart appears in one third-party article (agenticplug.ai) but only as a named participant in Google's separate UCP, not ACP — no vendor-specific Flipkart statement or ACP integration was found.

AP2 not found

The 60-organization contributor list published at the time of Google's AP2 donation to the FIDO Alliance (April 2026) includes payment processors, card networks, and merchants such as Mastercard, PayPal, Adyen, Etsy, and Worldpay — but Flipkart does not appear among them. No Flipkart-specific AP2 documentation, endpoint, or partnership announcement was found. Not confirmed absent via a Flipkart-issued statement; chosen not_found because the only evidence examined is the absence of Flipkart from the public contributor list.

MCP unable to verify

No usable finding available for this protocol (no legitimate scan available within the candidate window).

MPP not found

No evidence that Flipkart has adopted or is a launch partner for MPP. Known launch partners include Anthropic, OpenAI, Shopify, Alchemy, Dune Analytics, Cloudflare, Visa, and MultiversX — all distinct from Flipkart. No Flipkart-specific MPP documentation, announcement, or integration was found across both searches.

NLWeb not found

No evidence that Flipkart has implemented NLWeb. Microsoft's own NLWeb pioneer profiles name Tripadvisor, Delish, O'Reilly Media, Shopify, Allrecipes, and Inception as early adopters — Flipkart does not appear in any of these lists. The 2017 Flipkart–Microsoft Azure cloud partnership is unrelated to NLWeb. Not confirmed_absent because Flipkart has not issued its own statement on the matter; the evidence is simply absence of any adoption signal.

UCP unable to verify

No usable finding available for this protocol (no legitimate scan available within the candidate window).

WebMCP not found

No evidence found of Flipkart implementing or piloting WebMCP. The protocol is a Google/Chrome early-preview experiment (origin trial starting Chrome 149) with no publicly named retail or e-commerce launch partners; Chrome's own announcements reference unnamed 'global consumer brands experimenting' without identifying Flipkart. The not_found status is chosen rather than confirmed_absent because Flipkart has made no vendor-specific statement on the subject — absence of named participation is not the same as a declared rejection.

x402 not found

No evidence found that Flipkart has adopted or announced support for the x402 protocol. Known launch and early partners include Coinbase, Cloudflare, Stripe, Zuplo, and Stellar; Flipkart does not appear in any of these lists. The only Flipkart result surfaced in the search was an unrelated retail sale promotion, confirming there is no x402-related activity at flipkart.com.

openai_apps_sdk not found

Searches against OpenAI's ChatGPT app directory (chatgpt.com/apps) and related announcements returned no evidence of a Flipkart-built app on the platform. Named launch partners include Canva, Spotify, Zillow, Booking.com, and DoorDash — Flipkart does not appear among them. Flipkart's publicly known AI feature ('Flippi') is an internal shopping assistant within its own app, not a ChatGPT Apps SDK integration.

proprietary confirmed present

Supply-side seller and partner management: product listing creation and updates, order fulfillment workflows, return management, and aggregator/partner-managed multi-seller account access via OAuth scopes. Does not cover consumer-facing product discovery or affiliate publishing.

Flipkart Marketplace Seller API v3.0 is a proprietary REST API documented at seller.flipkart.com. Access requires prior Flipkart approval; only authorized sellers, aggregators, and vendor-partners are issued credentials. Covers listing management, order fulfillment, and returns but not consumer-facing or affiliate surfaces.

proprietary unable to verify

Flipkart Affiliate API v1.0 documentation still exists at affiliate.flipkart.com, but multiple third-party sources (2025-2026) report that Flipkart has discontinued its public affiliate program sign-ups. No official deprecation notice from Flipkart itself was found, so confirmed_absent is not warranted, but whether the API remains actively issuable to new users cannot be verified — hence unable_to_verify rather than not_found.

self_declared_discovery unable to verify

Direct HTTP checks to flipkart.com for all standard self-declaration paths (llms.txt, AGENTS.md, agents.md, /.well-known/agent, /.well-known/ai-plugin.json, /.well-known/agent-card.json) returned HTTP 000 (connection blocked/refused), meaning the domain actively blocks automated requests from this environment. No web search returned any evidence that Flipkart has published any such file; a Business Standard article from Nov 2025 quotes Flipkart as 'evaluating ways to refine LLM optimisation' but cites no published discovery file. Because the direct checks were structurally blocked rather than returning a 404 or actual content, not_found cannot be asserted with confidence.

Summary

Has agent interface: partial

Attempt direct contact with Flipkart's seller/partner onboarding team via seller.flipkart.com to request API credentials and clarify whether any agentic or MCP-compatible interface is on their roadmap; separately, seek official confirmation on the current status of the affiliate API program before treating it as a viable integration path.

AgentContext

Verified discrepancies

availability discrepancy active

Vendor claim: Flipkart advertises products at deep-discount sale prices (e.g., iPhone 16 models during Big Billion Days) and allows customers to place orders at those advertised prices.

What actually happens: Thousands of customers who successfully placed orders for advertised iPhone 16 and iPhone 16 Pro units during Flipkart's Big Billion Days 2025 sale had their orders subsequently cancelled, with Flipkart citing vague 'payment failures' or stock issues — while continuing to run the same deep-discount advertisements. This constitutes a pattern where inventory is displayed and orderable but is not actually fulfilled at the advertised conditions.

Agent guidance: When completing a purchase on Flipkart during promotional/sale events, do not treat a confirmed order as a completed transaction. Verify actual shipment confirmation before reporting success to the user, and alert the user that high-demand discounted items (especially electronics) are at elevated risk of post-order cancellation with vague justifications despite the order appearing confirmed at checkout.

last checked 2026-06-30

policy discrepancy active

Vendor claim: Flipkart's published cancellation policy states that customers can cancel orders before dispatch, with cancellations free within a defined window. The policy does not prominently state that a cancellation fee will be charged, nor does it clearly specify its amount or which users and products it applies to at the point of purchase.

What actually happens: In practice, Flipkart charges a cancellation fee of ₹20–₹499 after a short 'free cancellation window' (often 24 hours), deducted directly from the refund. The fee amount and applicability vary by product category and the customer's account history of prior cancellations and returns, making actual enforcement opaque and inconsistent. Flipkart explicitly reserves the right to accept, deny, or waive cancellations and fees at its sole discretion. A Mumbai District Consumer Court (DCDRC) found Flipkart guilty of deficiency in service and unfair trade practice in February 2024 for unilaterally cancelling a confirmed order without adequate remedy.

Agent guidance: Before initiating any cancellation on behalf of a user, explicitly check whether a cancellation fee applies to that specific order and surface the exact fee amount to the user for confirmation before proceeding. Do not assume cancellation is free based on Flipkart's headline policy language. If the fee amount cannot be confirmed in the UI prior to cancellation, escalate to the user rather than self-executing the cancellation.

last checked 2026-06-30

undisclosed constraint discrepancy active

Vendor claim: Flipkart displays products as available and allows users to proceed toward purchase without prominently disclosing upfront that delivery may be entirely unavailable to a given PIN code; the platform implies nationwide or broad delivery capability as a default shopping experience.

What actually happens: Numerous users report that after selecting products and entering their delivery address, Flipkart returns 'not deliverable to this PIN code' errors mid-checkout — including in major urban areas and IT hubs. During high-traffic sale events the problem is especially acute, with broad swaths of previously serviceable PIN codes suddenly becoming unserviceable without any prior notice or upfront filter. An agent attempting to complete a purchase would only encounter this constraint after product selection, potentially after payment initiation.

Agent guidance: Before attempting to add an item to cart or proceed to checkout, an agent should explicitly check PIN code deliverability for the specific product by entering the destination PIN code on the product page and confirming a valid delivery date is returned. If the platform returns 'not deliverable' or no delivery date, the agent should halt the transaction immediately and report back to the user rather than assuming the error is transient or retrying payment steps.

last checked 2026-06-30

Human handoff required for

Escalate to a human when a Flipkart order for a high-demand discounted product (especially electronics during promotional sale events such as Big Billion Days) shows 'order confirmed' status but no shipment confirmation has been issued, as the confirmed order may be subsequently cancelled by Flipkart under vague pretexts while the same discount advertisement continues running.

Escalate to a human before executing a cancellation on any Flipkart order where the exact cancellation fee amount (₹20–₹499) cannot be confirmed in the UI prior to submission, since the published policy does not prominently disclose this fee and its applicability varies opaquely by product category and user account history.

Escalate to a human when Flipkart returns a 'not deliverable to this PIN code' error mid-checkout after product selection has already been made, particularly during high-traffic sale events when previously serviceable PIN codes may go dark without prior notice, rather than retrying payment steps or assuming the error is transient.

Five categories were checked for Flipkart (flipkart.com): (1) discrepancy_pricing — searched for hidden fees or checkout price gaps; no verified buyer-facing pricing discrepancy was found, though CCI competition-law proceedings against Flipkart regarding seller pricing practices were noted as out of scope for buyer-facing checkout integrity. (2) discrepancy_availability — a verified finding was confirmed via a September 2025 InGovern letter to India's Ministry of Consumer Affairs documenting large-scale post-confirmation order cancellations during Big Billion Days 2025. (3) discrepancy_identity — no scans were available for this category, so whether Flipkart has identity-related discrepancies (e.g., seller impersonation, counterfeit storefronts) remains unchecked and cannot be assessed. (4) discrepancy_policy — a verified finding was confirmed: Flipkart's cancellation fee structure (₹20–₹499) is not prominently disclosed in the published policy, and a February 2024 Mumbai consumer court ruling confirmed unfair trade practice in order cancellation handling. (5) discrepancy_undisclosed_constraint — a verified finding was confirmed: PIN code deliverability constraints are only surfaced mid-checkout rather than at the browsing or product-selection stage, a pattern documented across multiple years and especially severe during sale events.