concur.com

SAP (Concur's parent) is a confirmed contributor to the A2A protocol and references it in SAP-level innovation guides and training materials, but no evidence was found of an A2A-specific endpoint, capability, or implementation scoped to concur.com or SAP Concur as a product. The A2A references found relate to SAP's broader Joule orchestrator and enterprise agent platform, not to the Concur travel-and-expense product surface. Named A2A launch partners include Atlassian, Box, PayPal, Salesforce, Workday, and SAP at the enterprise platform level — none specifically Concur.

No evidence found that SAP Concur (concur.com) participates in or has integrated the Agentic Commerce Protocol. Known ACP launch partners include Shopify merchants (Glossier, SKIMS, Spanx, Vuori), Etsy sellers, URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all consumer retail merchants, a category Concur does not belong to. Concur's 2025–2026 AI efforts are focused on Joule-based expense automation and an Amex GBT partnership, with no mention of ACP.

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

No official MCP server published or documented by SAP Concur (concur.com) was found. All MCP servers found are third-party projects: CData Software offers a commercial MCP connector for SAP Concur data, and independent developers (bachstudio, thisislance98) have published community wrappers against the SAP Concur REST API. SAP Concur's own developer portal (developer.concur.com) shows no MCP-related content. Their existence signals demand but is not evidence of an official concur.com offering.

MPP (Multi-rail Machine Payment Settlement via Stripe + Tempo) launched as an open standard for machine-to-machine payments, with early adopters including MultiversX and other blockchain/API-monetization platforms. No evidence found of SAP Concur (concur.com) participating as a launch partner or implementing MPP anywhere in its travel, expense, or invoice product lines. SAP Concur's recent payment-related announcements center on Joule AI, American Express GBT, and Visa integrations — not MPP.

No evidence that concur.com is an NLWeb participant. The confirmed NLWeb pioneer/partner list includes Chicago Public Media, Common Sense Media, DDM (Allrecipes & Serious Eats), Milvus, Shopify, and Snowflake — SAP Concur does not appear in any published launch partner announcement. A secondary search found no connection between NLWeb and SAP Concur. Status is not_found rather than confirmed_absent because no vendor-specific statement from SAP Concur ruling out NLWeb was located.

No evidence found of SAP Concur (concur.com) implementing, announcing, or participating in the Universal Commerce Protocol. UCP's documented early adopters and collaborators are Google, Shopify, Salesforce, and Eco — all distinct from Concur's travel-and-expense domain. Searches targeting concur.com specifically returned no UCP mentions; the distinction between not_found and confirmed_absent is that Concur has made no vendor-specific statement either way.

No evidence that concur.com has implemented or announced WebMCP support. WebMCP early-preview coverage (Chrome for Developers, particula.tech, leadgen-economy.com) names no travel or expense management vendors among early adopters; HubSpot and Stripe-adjacent tools appear in that context instead. Concur's own 2026 AI announcements (SAP Concur Fusion 2026) describe agentic AI capabilities internal to their platform, not browser-layer WebMCP tool exposure.

No evidence that SAP Concur (concur.com) is involved in the x402 protocol ecosystem as a launch partner, adopter, or integrator. Known x402 launch partners include Cloudflare, Amazon Bedrock (AgentCore), Google, Stellar, and Solana — none of the search results mention Concur or SAP in that context. Concur's integration ecosystem focuses on ERP, HR, and payroll connectors, with no indication of stablecoin or HTTP 402 payment protocol adoption.

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

REST API suite covering expense reports, travel requests, invoices, receipts, user/profile data, travel itineraries, budgets, and spend documents; accessed by SAP Concur App Center partners via OAuth 2.0 scoped tokens; full read/write not available to all callers — scope determines which product areas and operations are accessible

SAP Concur exposes a large proprietary REST API suite documented at developer.concur.com, covering Expense (v4), Travel Request (v4), Invoice, Receipt, Profile, Budget, and Itinerary APIs among others. Access is gated behind the App Center partner enrollment process, which requires completing a Partner Project Readiness Form and assignment of a technical project manager — not self-serve. Documentation is publicly viewable but credentials are partner-only.

Direct HTTP checks for all standard self-declaration paths (llms.txt, AGENTS.md, /.well-known/agent, /.well-known/ai-plugin.json, /.well-known/mcp.json) on concur.com, www.concur.com, and developer.concur.com all timed out at DNS resolution — the sandbox has no outbound network access to concur.com's infrastructure, making a fetch-based check impossible. Web searches for site:concur.com combined with these paths returned no results pointing to any such files, and no third-party sources reference Concur/SAP Concur publishing any agent self-declaration files. Unable to confirm presence or absence via direct inspection.