/vendor/allegro/AgentRouting.json or
/vendor/allegro/AgentContext.json directly.
allegro.pl
Overview
Does allegro.pl support MCP?
No confirmed MCP support was found for allegro.pl as of 2026-06-30.
What agentic protocols does allegro.pl support?
As of 2026-06-30, allegro.pl has confirmed support for proprietary.
Is allegro.pl's API publicly accessible or partner-gated?
Open.
Does allegro.pl explicitly prohibit automated access?
Yes. allegro.pl's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is allegro.pl agent-ready?
Partial. allegro.pl supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence that allegro.pl is a launch partner, pilot participant, or has any documented relationship with the AP2/Agent Payments Protocol initiative. Known AP2 contributors include Google, Mastercard, and FIDO Alliance working groups. Allegro's developer surface is a conventional REST API with OAuth2 authentication, with no indication of cryptographic payment-consent mandate adoption.
No official MCP server offered by Allegro (allegro.pl) was found. The allegro.tech engineering blog published a December 2025 article about running an MCP server on the JVM with Spring AI and GitHub Copilot — but this is an internal developer quickstart/tutorial, not a publicly callable Allegro MCP endpoint. Third-party community projects exist (notably github.com/piotrlinski/allegro-open-mcp-server, explicitly self-described as unaffiliated with Allegro, and Apify-hosted scrapers), none of which are vendor-sanctioned. Allegro's official developer surface remains its REST API at developer.allegro.pl.
No evidence that allegro.pl has implemented or announced NLWeb. The confirmed early launch partners from Microsoft's rollout include Shopify, TripAdvisor, Eventbrite, O'Reilly, Chicago Public Media, Hearst, and Snowflake — allegro.pl does not appear in any of these lists. No allegro.pl /ask or /mcp endpoint, partner announcement, or developer documentation referencing NLWeb was found.
No evidence that allegro.pl has implemented or announced WebMCP support. Searches for WebMCP launch partners returned Chrome for Developers documentation and general industry commentary — not allegro.pl. Allegro's developer portal (developer.allegro.pl) focuses exclusively on its REST API with OAuth 2.0, with no mention of browser-layer agent tooling.
No evidence found connecting allegro.pl to the x402 protocol. Known launch-ecosystem participants include Coinbase, Cloudflare, Stellar, Stripe, and various developer-tooling projects — allegro.pl does not appear in any partner list, launch announcement, or community resource directory. Allegro.pl is a traditional e-commerce marketplace with no publicly documented crypto or stablecoin payment infrastructure; there is no vendor-specific statement, deprecation notice, or integration that would support any status other than not_found.
Original confirmed_present claim lacked any supporting detail (no role, no notes) and was discarded pending re-verification.
Seller-side marketplace REST API covering offer/listing management, order processing, returns, inventory, account health, and buyer messaging; also provides a sandbox environment for development. Previously a legacy SOAP/WebAPI was offered but was deprecated in 2020 and replaced by this REST API as the sole supported integration method.
Allegro's REST API is documented at developer.allegro.pl and is the only currently supported programmatic interface for integrating with the Allegro marketplace. The legacy WebAPI (SOAP/XML) was retired in 2020. A sandbox environment is available for testing before going to production.
Direct HTTP probing of allegro.pl for /llms.txt, /agents.txt, /AGENTS.md, /.well-known/agent, and /.well-known/agent-configuration all timed out (network-level block on outbound requests from this environment), making it impossible to confirm whether these files exist or not. Searches returned no evidence that allegro.pl has published any of these self-declaration files; the only allegro-related result was a GitHub repo for allegro/allms (an LLM querying library) with no relevance to domain-level agent discovery. No vendor-specific evidence of self-declared discovery files was found.
Summary
Has agent interface: partial
Verify the OpenAI Apps SDK integration detail — the protocol entry contains formatting anomalies in the protocol name field (',openai_ apps_ sdk') and lacks endpoint, role, or auth detail, so a targeted follow-up check against Allegro's official developer documentation and OpenAI's plugin/app directory is needed to confirm the nature and scope of this integration before treating it as a usable agent-callable surface.
AgentContext
Verified discrepancies
Vendor claim: Allegro presents buyers with delivery options as configured by sellers, implying a full and neutral display of all available shipping methods at checkout.
What actually happens: Independent investigation and a January 2026 court ruling found that Allegro was replacing or suppressing seller-configured delivery options at checkout in favour of its own Allegro Delivery service. For example, a buyer-selected InPost locker pick-up point was silently substituted with the nearest Allegro-branded machine, without the buyer's knowledge or explicit consent.
Agent guidance: When completing a purchase on allegro.pl, do not assume the delivery options shown at checkout represent all options the seller has configured. Explicitly verify available delivery methods against the seller's full listing before confirming an order, and if a preferred carrier (e.g. a specific InPost locker) has been silently substituted, treat the transaction as incomplete and surface the substitution to the user for explicit re-confirmation before proceeding.
- A January 28, 2026 provisional injunction from the Warsaw District Court (brought by the Consumers Forum Foundation) required Allegro to display the full list of seller-offered delivery methods without preference, confirming the platform had been suppressing alternatives in favour of Allegro Delivery.
- Poland's consumer regulator UOKiK investigated Allegro in spring 2025 over how it presents delivery options after documented reports that Allegro Delivery was being promoted at the expense of other seller-configured carriers at checkout.
Human handoff required for
Confirm delivery method with user when a selected carrier or pick-up point (e.g. a specific InPost locker) has been silently substituted at checkout with an Allegro Delivery option the user did not explicitly choose
Escalate to a human when the delivery options displayed at checkout do not match the full set of delivery methods visible on the seller's original listing, as Allegro has been confirmed to suppress or replace seller-configured options
Pause and seek user re-confirmation before finalising any order where Allegro's checkout presents a single or narrowed set of delivery options that cannot be cross-checked against the seller's listing, since the injunction compliance status and remediation completeness as of mid-2026 is unverified
Five categories were checked: (1) discrepancy_pricing — searched for hidden fees or checkout price inflation; no verified finding was identified, only an unrelated 2022 UOKiK fine about contract amendment clauses. (2) discrepancy_availability — searched for ghost inventory or bait-and-switch listings; no platform-level systemic finding was identified, only isolated bad-actor seller cases. (3) discrepancy_identity — searched for merchant-of-record ambiguity or counterparty misidentification; no structural or regulatory finding was identified, with Allegro's help documentation clearly naming the individual seller as counterparty. (4) discrepancy_policy — searched for gaps between stated and enforced cancellation, refund, and returns policies; no independently verified systemic discrepancy was found, though a policy consolidation took effect June 30, 2025. (5) discrepancy_undisclosed_constraint — a significant finding was confirmed: Allegro was suppressing seller-configured delivery options at checkout in favour of its own Allegro Delivery service, resulting in a January 2026 Warsaw District Court provisional injunction; this is the sole category with a confirmed finding and drives all handoff triggers above.