Frequently Asked Questions ¶

This page answers specific questions that are not covered in the EAP overview. Unless noted otherwise, these answers describe EAP's target-state operating model. For current availability and delivery targets, use Status.

Can CCPS Teams Use A Different Agent Harness? ¶

No. EAP supports Codex as its only agent harness.

Can CCPS Teams Use Different Models? ¶

Yes. A model must be both available through Cisco Collab LLM Proxy and supported by EAP. See LLM proxy and models for available models and the request process.

Does BYOK Require A Literal API Key? ¶

No. Bring Your Own Key (BYOK) is the name of the operating model. Each CCPS team provides its own Cisco Collab LLM Proxy application credentials, but the supplied credential is not necessarily a literal API key.

Can CCPS Teams Reuse EAP Backend Infrastructure For Other Projects? ¶

No. There are no current plans to offer EAP's backend infrastructure as a general-purpose platform for code-first projects.

Can An EAP Agent Fetch Web Content? ¶

Yes. Network egress is denied by default, so every destination must be approved. The recommended approach is to use an MCP server that limits requests to approved public and internal sources rather than allowlisting destinations for Codex to reach directly.

Can CCPS Teams Configure MCP Servers That Are Not In The MCP Catalog? ¶

Yes. CCPS teams add or update MCP server entries in their Agent Registry YAML files in the EAP-owned enterprise-agent-platform-registry repo. EAP reviews each new or changed MCP server configuration before deployment and either approves or rejects it.