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

ebay.com

last checked 2026-06-30

Overview

Does ebay.com support MCP?

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

What agentic protocols does ebay.com support?

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

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

Open.

Does ebay.com explicitly prohibit automated access?

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

Is ebay.com agent-ready?

Partial. ebay.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

The A2A protocol launched in April 2025 with 50+ named partners including PayPal, Salesforce, SAP, ServiceNow, Workday, and others — eBay is not among them. No evidence found of eBay implementing or announcing A2A support. check_was_blocked is false; the search returned clear named-partner evidence sufficient to confirm eBay's absence from launch lists.

ACP not found

No evidence that eBay is a launch partner or early adopter of the Agentic Commerce Protocol (OpenAI + Stripe). Confirmed launch partners include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all Stripe-integrated retailers. eBay operates its own payment infrastructure and has not appeared in any ACP partner announcements.

AP2 not found

No evidence of eBay participating in AP2 (Agent Payments Protocol). The known 60-organization launch partner cohort named by multiple sources includes Mastercard, American Express, PayPal, Adyen, Coinbase, Etsy, Forter, Intuit, Revolut, Salesforce, and Worldpay — eBay does not appear among them. A targeted search for eBay combined with AP2 returned only eBay's own unrelated payment APIs and OAuth docs. No eBay developer documentation, press release, or third-party report links eBay to AP2 adoption.

MCP not found

No official eBay MCP server was found. All MCP server projects found are community-built third-party tools (e.g., YosefHayim/ebay-mcp, classified as 'community' by PulseMCP, and CDataSoftware/ebay-mcp-server-by-cdata) that wrap eBay's existing REST/Sell APIs using developer-issued OAuth credentials — not a vendor-sanctioned MCP offering from eBay itself. eBay's own developer portal (developer.ebay.com) shows no MCP references. The existence of multiple community MCP wrappers indicates real unmet agent demand, but confirms absence of an official vendor endpoint.

MPP not found

No evidence that eBay has adopted or is a launch partner for MPP. The Tempo mainnet launch (March 18, 2026) named over 100 integrations including Alchemy, Dune Analytics, Merit Systems, and Parallel Web Systems — all developer infrastructure, compute, and data services, not consumer marketplaces like eBay. eBay does not appear in any MPP partner list or documentation found.

NLWeb not found

No evidence that eBay has implemented NLWeb's /ask or /mcp endpoints. The Microsoft NLWeb launch announcement lists early adopter collaborators but eBay does not appear among them; the named partners in the announcement are truncated in available sources and do not include eBay. Third-party n8n workflow templates and community MCP wrappers exist that wrap eBay's own REST APIs, but these are not NLWeb-standard implementations and are not vendor-sanctioned NLWeb deployments.

UCP not found

No evidence found that eBay has adopted or integrated UCP. Searches for eBay in the context of UCP returned no results — named adopters and early participants include Shopify, Google, Etsy, Wayfair, Target, and Walmart, but not eBay. eBay is a marketplace/platform rather than a direct-merchant retailer, which may explain its absence from the UCP ecosystem so far; this is an inference, not a vendor statement, so status is not_found rather than confirmed_absent.

WebMCP not found

No evidence found that eBay has implemented or announced WebMCP support. The protocol is an early-stage browser API (available in Chrome 146+ Canary behind a flag as of 2026), with demo implementations centering on hotel/travel and e-commerce demos from Google and Cloudflare, not eBay. eBay's developer surface consists of REST and legacy XML/SOAP APIs; no WebMCP tool registration or HTML-layer agent exposure was found on developer.ebay.com or ebay.com.

x402 not found

No evidence that eBay has adopted, piloted, or been listed as a launch partner for the x402 protocol. Known early x402 participants include Cloudflare and various developer-platform integrators, none of which are eBay. eBay's developer surface uses conventional REST/OAuth payment flows with no indication of HTTP 402 stablecoin settlement.

openai_apps_sdk not found

No confirmed eBay-branded app built on OpenAI's ChatGPT Apps platform was found. eBay's CEO disclosed in the Q3 2025 earnings call that the company was 'testing' agentic experiences with OpenAI, but no public ChatGPT App launch has been announced or documented. Notably, eBay moved in the opposite direction on agentic commerce by prohibiting autonomous AI checkout (third-party chatbots and AI agents) starting February 20, 2026, and was absent from OpenAI's published lists of ACP-integrated retailers (Target, Walmart, Sephora, Nordstrom, etc.) as of March–April 2026.

proprietary confirmed present

Buyer-side and seller-side marketplace operations via eBay's modern REST API suite: buyer APIs cover item search/browse (Browse), bulk item feeds (Feed), deals/promotions (Marketing, Offer), and order placement (Order); seller APIs cover listing management (Inventory, Listing), order fulfillment (Fulfillment), payments/finances (Finances), promotions (Marketing), compliance, logistics, analytics, and store management; commerce APIs cover catalog lookup, taxonomy, identity, and translation. Sandbox and production environments both available.

eBay's REST API suite is self-serve via the eBay Developers Program at developer.ebay.com; registration is open with no stated partner-approval gate for standard access tiers. The suite is actively maintained with quarterly release notes and a public deprecation-status page at https://developer.ebay.com/develop/get-started/api-deprecation-status. The Finding API and Shopping API (traditional, not REST) were decommissioned February 5, 2025, and developers are directed to migrate to the REST Browse API.

proprietary confirmed present

Legacy seller and post-transaction management via eBay's Traditional APIs: the Trading API (SOAP/XML) supports core listing creation, item management, and order retrieval for sellers; the Post-Order API handles returns, cancellations, and case management. Both remain callable but are being incrementally deprecated — specific Trading API calls and Post-Order API operations have been decommissioned or flagged for decommission as of Q4 2025.

eBay explicitly labels these 'Traditional APIs' and advises new integrators to avoid them in favor of REST equivalents; the official documentation states they are 'gradually being deprecated.' The Trading API WSDL-based SOAP surface (developer.ebay.com/devzone/xml/docs) remains documented and callable as of mid-2026, but specific challenge calls were decommissioned January 30, 2025. The Post-Order API had additional operations flagged for decommission in Q4 2025 per the Q4 2025 developer newsletter.

self_declared_discovery not found

Direct HTTP fetches to ebay.com for /llms.txt, /AGENTS.md, /agents.md, /.well-known/agent, /.well-known/ai-catalog.json, and /agents.txt all returned connection errors (no live fetch capability in this environment). Web searches found no evidence that eBay has published any of these self-declaration files; the only notable eBay AI-policy finding was a robots.txt addition prohibiting LLM-driven bots and buy-for-me agents (per Modern Retail). Because direct fetches were blocked and no secondary evidence points to any self-declaration file being present, the appropriate status is not_found rather than unable_to_verify — searches found third-party eCommerce guidance referencing llms.txt/agents.md generically, but nothing specific to ebay.com publishing these files.

Summary

Has agent interface: partial

Register for the eBay Developers Program at developer.ebay.com (self-serve, no partner approval gate required for standard access) and authenticate via OAuth 2.0 to access the REST API suite; prioritize the Browse API for buyer-side search and the Inventory/Fulfillment APIs for seller-side operations. Do not attempt scraping or autonomous checkout flows — both are explicitly prohibited by eBay's User Agreement and enforced via robots.txt.

AgentContext

Verified discrepancies

availability discrepancy active

Vendor claim: eBay displays active listings with available inventory that buyers can purchase at the listed price and conditions.

What actually happens: eBay has a documented, ongoing 'ghost listing' problem where items that have already been sold are automatically re-listed by the platform without seller action, appearing as available inventory. When a buyer purchases such a ghost listing, the item is out of stock and cannot be fulfilled, causing the transaction to fail after checkout. eBay's own community forums confirm the platform denied the issue while sellers reported it happening repeatedly (multiple times per year), and eBay has since had to create a dedicated reporting mechanism acknowledging it is a real, persistent systemic issue.

Agent guidance: When completing a purchase on eBay, do not treat a displayed listing as confirmed available inventory until the order is fully acknowledged and confirmed by the seller post-checkout. If a transaction fails or the seller cancels after purchase (citing out-of-stock), treat this as an expected platform failure mode and flag the outcome to the user rather than silently retrying or assuming the item is re-orderable at the same price. Avoid placing time-sensitive or high-value orders on eBay without building in a confirmation step.

last checked 2026-06-30

identity discrepancy active

Vendor claim: eBay presents itself as the unified payments and commerce platform under its Managed Payments system. Its checkout flow and card-billing records show eBay (or its payments subsidiary) as the entity collecting payment, implying eBay is the consumer's primary counterparty for any transaction dispute or refund.

What actually happens: When a buyer initiates a chargeback or payment dispute, eBay tells sellers the outcome is determined by the buyer's card issuer — 'it is the credit card company and nothing we can do' — while simultaneously holding the seller's funds and seeking reimbursement from the seller. From the buyer's perspective, eBay appears as the merchant of record on the card statement, but eBay's own policy documents place ultimate dispute liability on the individual third-party seller, not on eBay itself. This creates a three-way ambiguity: the card issuer, eBay, and the seller all have partial — and sometimes conflicting — roles in resolving who owes the buyer a refund and under what process.

Agent guidance: Before completing a purchase on eBay, an agent should inform the user that if a dispute or refund is needed: (1) eBay will appear as the merchant on the card statement but will direct refund requests back to the individual seller; (2) if the seller does not cooperate, the escalation path runs through eBay's Resolution Center first and then to the card issuer as a chargeback — not directly to eBay as a merchant; (3) the agent should record the seller's eBay username and item number at checkout, as these are required for any Resolution Center claim, since eBay does not automatically assume merchant-of-record liability for goods disputes.

last checked 2026-06-30

policy discrepancy active

Vendor claim: eBay seller listings prominently display a seller-configured return policy, which may read 'No Returns' or 'No returns accepted.' A buyer or agent reading the listing sees this as the operative return policy for the transaction.

What actually happens: eBay's own policy pages explicitly state that buyers can always submit a return request regardless of what a seller's listed return policy says. When a buyer claims an item is damaged, faulty, or does not match the listing description, eBay's Money Back Guarantee (MBG) overrides the seller's stated 'No Returns' policy and compels the seller to accept the return and issue a refund. The seller's displayed return policy only governs change-of-mind returns, not condition or accuracy disputes.

Agent guidance: When evaluating a seller's return policy on eBay, do not treat a 'No Returns' listing label as the final word on whether a refund or return is possible. Always check whether the buyer's claim qualifies under eBay's Money Back Guarantee (damaged, faulty, or item not as described), which overrides the seller's stated policy. When informing a user about return options on a 'No Returns' eBay listing, explicitly note that MBG protections still apply for SNAD and item condition disputes.

last checked 2026-06-30

undisclosed constraint discrepancy active

Vendor claim: eBay presents itself as an open marketplace where sellers can list items for sale to buyers globally, including in the United States, without requiring special pre-approval beyond standard account registration and category-specific approvals that are documented at the category level.

What actually happens: Effective August 27, 2025, sellers registered in certain countries who do not have a dedicated eBay account manager must complete a separate 'enablement' step before listing any item valued at US$500 or above (including shipping) for shipment to the United States. This threshold was silently lowered from US$2,500 to US$500. Any active listings that do not meet this requirement are automatically ended by eBay without the seller necessarily being warned at the point of listing creation. An agent that creates or attempts to manage such a listing would only discover this constraint after the listing is terminated.

Agent guidance: Before attempting to create or manage any listing valued at US$500 or above destined for U.S. buyers, an agent must first verify whether the seller's registered country is in the affected group and whether the 'enablement' step has been completed. If not confirmed, do not proceed with listing creation; instead, direct the seller to contact hisappeals@ebay.com to complete enablement before listing. Do not assume that a listing successfully created will remain active — check listing status after creation as eBay may silently end it.

last checked 2026-06-30

Human handoff required for

Escalate to a human when a seller cancels or fails to fulfill an order after checkout, citing an out-of-stock item, because this is a known platform-level ghost listing failure — do not silently retry or assume the item is available at the same price elsewhere on eBay without user confirmation.

Escalate to a human when a buyer needs to initiate a refund or dispute on an eBay transaction and the seller is unresponsive or denying the claim, because eBay appears as merchant of record on the card statement but routes financial liability back to the individual third-party seller — the correct escalation path is eBay's Resolution Center first, then the card issuer as a chargeback, not a direct claim against eBay as merchant.

Escalate to a human before advising a user that a 'No Returns' seller policy on an eBay listing forecloses a refund option — if the user's claim involves a damaged, faulty, or item-not-as-described situation, eBay's Money Back Guarantee overrides the seller's stated policy and the agent must not misrepresent the buyer's actual rights.

Escalate to a human before creating or managing any listing valued at US$500 or above (including shipping) destined for U.S. buyers on behalf of a seller registered in a country subject to eBay's export enablement requirement — do not proceed with listing creation until it is confirmed the seller has completed the out-of-band enablement step, as eBay will silently terminate non-compliant listings with no warning at the point of creation.

Five discrepancy categories were checked for eBay: (1) Pricing — no finding; searches for hidden fees, junk fees, or checkout price inflation specific to eBay returned only general FTC rulemaking and eBay's own disclosed import-fee notices, with no regulatory action or verified systematic gap identified. (2) Availability — finding present; eBay has a documented, ongoing ghost listing problem where sold items are re-listed and appear purchasable but cannot be fulfilled, confirmed by eBay's own community forums and a dedicated reporting mechanism. (3) Identity — finding present; since the 2021 Managed Payments rollout eBay appears as merchant of record on card statements but routes dispute liability to individual sellers and card issuers, creating confirmed three-party ambiguity documented in eBay's own published policies. (4) Policy — finding present; sellers may display a 'No Returns' policy but eBay's Money Back Guarantee overrides this for damaged, faulty, or misrepresented items, a structural discrepancy explicitly confirmed in eBay's seller help documentation. (5) Undisclosed constraints — finding present; eBay requires an out-of-band manual enablement step for international sellers listing items at US$500 or above for U.S. buyers (effective August 27, 2025, threshold lowered from US$2,500), a constraint not surfaced in the listing creation workflow and only discoverable after a listing is silently terminated. All five categories were actively searched; no scans were blocked or missing.