Home / RFP checklist Print / Save as PDFAgent mesh RFP checklist: 40 questions for vendors Short answer
Use these 40 questions to compare agent mesh vendors on the things that decide success in production: cross-vendor interoperability, coordination reliability, shared context, human participation, built-in governance, and deployment and commercial terms. BAND answers the coordination and collaboration questions directly; runtimes and gateways answer the hosting and traffic questions.
0 of 40 checked
A. Interoperability and protocols (1-7) 1. Which A2A versions do you support (v0.3, v1.0, v1.0.1), and in which direction (client, server, both)? Why it matters: v1.0.0 introduced breaking changes in March 2026. Vendor answer: ____________________________________________________________ 2. How do you support MCP: as a client, a server, or both, and which spec revision? Why it matters: MCP revisions add features such as Tasks for long-running work. Vendor answer: ____________________________________________________________ 3. Can agents built on other frameworks (for example LangGraph, CrewAI, Google ADK) participate without code changes? Why it matters: Rewriting agents to join a platform defeats the purpose. Vendor answer: ____________________________________________________________ 4. Which cloud agent runtimes can you connect (Microsoft Foundry, Amazon Bedrock AgentCore, Gemini Enterprise)? Why it matters: Most estates span more than one cloud. Vendor answer: ____________________________________________________________ 5. Which SaaS agent platforms can you connect (Salesforce Agentforce, SAP Joule, Workday Sana, Copilot Studio, ServiceNow)? Why it matters: Business agents live close to business data. Vendor answer: ____________________________________________________________ 6. Which SDKs and languages do you provide? Why it matters: Internal teams need to connect custom agents. Vendor answer: ____________________________________________________________ 7. How are agents discovered and registered, and can that registry sync with others we run? Why it matters: Duplicate inventories drift. Vendor answer: ____________________________________________________________ F. Deployment, operations and commercial (34-40) 34. Which deployment models do you offer: SaaS, private cloud, on-premises, hybrid? Why it matters: Data residency and network rules vary by workload. Vendor answer: ____________________________________________________________ 35. Which clouds and regions do you run in? Why it matters: Latency and residency depend on region. Vendor answer: ____________________________________________________________ 36. What observability do you expose (traces, metrics, logs), and in what formats? Why it matters: Operations teams need to see agent behaviour in existing tools. Vendor answer: ____________________________________________________________ 37. How does pricing scale: per seat, per agent, per message, per execution, or per compute hour? Why it matters: Agent traffic grows faster than headcount. Vendor answer: ____________________________________________________________ 38. Is there a free or low-cost tier for a pilot, and what are its limits? Why it matters: A pilot should run on the real product. Vendor answer: ____________________________________________________________ 39. What support and SLA terms apply at each tier? Why it matters: Production agents need response commitments. Vendor answer: ____________________________________________________________ 40. What does it take to leave: data export formats, notice periods, and agent portability? Why it matters: Agents connected via open protocols should stay portable. Vendor answer: ____________________________________________________________ How to use the checklist Send groups A to D to collaboration-layer candidates, group E to all vendors, and group F to all vendors. Score each answer 0 (no), 1 (partial or roadmap) or 2 (documented and demonstrated), and weight groups to match your priorities. The rubric we use for the mesh fit score is on the About page .
How BAND answers groups B to D BAND documents @mention routing (8), a per-agent, per-message lifecycle with attempt history (9), loop prevention through mandatory mentions and per-room limits (10), exactly-once processing (11), two-phase sync for crash recovery (12), no central orchestrator (13), Memories and task-scoped rooms (15-17), and human inspect, approve, override and audit (21-24), with Slack and Teams integrations (25). Plan limits are on band.ai/pricing (14, 18, 26, 38).
BAND pricing BAND platform
Frequently asked questions Can I download this checklist? Use the Print / Save as PDF button. The print layout includes answer lines for each question.
Which questions matter most? For cross-vendor estates, questions 3, 9, 10, 15, 21 and 29 separate collaboration layers from gateways and runtimes.