seloger.com

No evidence that seloger.com participates in the Agent2Agent protocol. The A2A launch partner list (April 2025, via Google Cloud / Linux Foundation) named enterprise technology vendors such as Atlassian, Box, Salesforce, SAP, and Workday — seloger.com is absent. The only agent-adjacent tooling found for seloger.com is third-party, unsanctioned MCP scrapers on Apify, with no official developer API or A2A surface published by SeLoger itself.

No evidence found that seloger.com (a French real estate listing portal) has adopted or announced support for the Agentic Commerce Protocol. The confirmed ACP launch partners include Salesforce, Stripe-integrated merchants, and OpenAI's direct commerce integrations — seloger.com does not appear among them. Real estate listing platforms are not among the initial ACP adopter segments, and no vendor-specific announcement or documentation was located.

No evidence of seloger.com appearing in any AP2 launch partner list or documentation. Known AP2 participants (as of FIDO Alliance donation, April 2026) are payment/fintech/Web3 entities: Adyen, Nexi, Worldpay, Revolut, Coinbase, Metamask, Ethereum Foundation — no consumer real estate portals. As a French property-listing platform, seloger.com has no apparent role in AP2's payments-consent infrastructure.

All MCP-labeled results for seloger.com originate from third-party Apify scraper actors (e.g., apify.com/data_forge_org/apify-seloger/api/mcp, apify.com/stealth_mode/seloger-search-scraper/api/mcp) — these are unsanctioned scrapers, not a vendor-published interface. No official seloger.com MCP server was found in the official MCP registry (registry.modelcontextprotocol.io), on glama.ai, or on mcpservers.org, and seloger.com's own professional/developer-facing properties (pro.seloger.com, aide-dev.seloger.com) show no MCP offering. Chosen not_found rather than confirmed_absent because no vendor-specific deprecation notice exists — absence of evidence only.

No evidence found that seloger.com participates in the MPP (Stripe + Tempo multi-rail machine payment settlement) protocol in any capacity. Known early launch partners cited in public sources include Visa, Mastercard, Shopify, and OpenAI — no consumer real estate portals and no seloger.com appear anywhere in launch partner lists or on the mpp.dev services directory. This is not_found rather than confirmed_absent because seloger.com has made no vendor-specific statement on the matter.

No evidence was found of SeLoger.com implementing or announcing support for the Universal Commerce Protocol. Search results for UCP/agentic commerce in the real estate context returned only general UCP ecosystem coverage (Google, Shopify, Walmart, Target, Salesforce, commercetools) with no mention of SeLoger. SeLoger is a French property listing portal whose core product is residential real estate search and lead generation — not a transactional commerce merchant in the product-retail sense that UCP is currently targeting. Not_found is used rather than confirmed_absent because no SeLoger-specific statement or deprecation notice was found; the absence is based on a lack of any evidence, not a vendor declaration.

No evidence found that seloger.com has implemented or announced WebMCP support. The protocol is at early preview stage (Google Chrome), with no public list of named launch partners that includes seloger.com. Named early participants in WebMCP coverage were generic illustrative examples (flight booking, support tickets), not specific vendors. This is a not_found, not confirmed_absent, as seloger.com has made no vendor-specific statement either way.

No evidence found connecting seloger.com to the x402 protocol. Coinbase's announced launch partners for x402 include AWS, Anthropic, Circle, NEAR, and Cloudflare — none of which are SeLoger or its parent group. SeLoger is a French real estate classifieds platform with no identified crypto payment or agentic commerce surface. Not confirmed_absent because no SeLoger-specific statement or deprecation notice was found; rather, the vendor simply does not appear in any x402 partner or ecosystem context.

No evidence of a SeLoger (seloger.com) integration built on the OpenAI Apps SDK or listed in the ChatGPT apps store was found. A third-party GPT named 'SeLoger : Agent Immo Expert' exists at chatgpt.com/g/g-EncPCUyNh-seloger-agent-immo-expert, but this appears to be a community-built GPT not an official SeLoger-published Apps SDK integration, and there is no indication it is sanctioned by seloger.com. Pilot partners publicly named by OpenAI (e.g. Booking.com, Canva, Zillow) do not include SeLoger.

Listing publication and management API (called 'API CaaS' / 'Connectivité Annonces et Services') for professional real estate software vendors (logiciels immobiliers) to push property listings in real time to SeLoger and affiliated AVIV Group portals (Logic-Immo, Belles Demeures, Lux Residence); does not provide public property search data access

SeLoger (AVIV Group) operates a proprietary partner API suite under the brand 'ACP' (Connectivité Annonces et Services), with the specific product called 'API CaaS', documented for integration by real estate software vendors. Multiple third-party integrators (Apimo, Orisha/Immofacile) confirm real integrations. No public endpoint URL or docs URL is published openly; access requires a commercial partnership with SeLoger. There is no publicly accessible API for consumer-side listing search — multiple sources explicitly confirm SeLoger publishes no public API for data extraction.

Direct HTTP fetches of seloger.com were blocked by detection/timeout, making it impossible to confirm or rule out files at standard paths (e.g., /llms.txt, /AGENTS.md, /.well-known/agent). Web searches found no references to seloger.com publishing any self-declaration file; third-party results for seloger.com agent-related queries surfaced only unofficial scraper tools (Apify actors, RapidAPI wrappers) with no vendor-published discovery artifact. Status is not_found rather than unable_to_verify because the available evidence — including general web-indexed content — shows no trace of such a file, and the blocked direct-fetch case applies to an infrastructure check rather than a documentation or indexed-content check.