Your company already runs a mature inventory agent. A new multi-agent fulfillment solution must use it without rewriting it, while also attaching new MCP tools for carrier APIs. Which integration approach is best?
Select an answer to reveal the explanation.
Short Explanation
You should reuse the mature inventory agent through secure Agent2Agent and/or MCP-compatible interfaces, then add carrier APIs as MCP tools the fulfillment orchestrator can call. Don’t paste secrets into prompts, rebuild a working agent, or make users copy data by hand.
Full Explanation
Integrating the existing inventory agent securely via Agent2Agent and/or MCP-compatible interfaces is correct because developers should reuse stable agents in multi-agent solutions while building tool ecosystems for new capabilities. Copying API keys into prompts is incorrect because distributing secrets via prompts is insecure. Reimplementing the inventory agent from scratch is incorrect because unnecessary rewrites delay delivery when a stable agent exists. Manual browser copying is incorrect because manual UI copy is not orchestration. Define auth, contracts, and error handling at the integration boundary; treat the legacy agent as a bounded capability.