bapXhost
Connect or operate business workloads that use bapXhost while bapX remains the hosted control and coordination layer.
How it fits into bapX
bapXhost is listed under Hosting and infrastructure. Connections belong to a business and are scoped to the projects, people, agents, and automations that the business authorises.
Use Platform to manage connection ownership and credentials. Use Agents to select the connection during business work, and use MCP permissions when the capability is exposed through an MCP server or tool.
Credentials and access
- Bring credentials for the external provider when the connection requires them.
- Keep credentials at business or project scope; do not place secrets in project Markdown, source files, or chat messages.
- Grant only the agents, automations, and people that need this connection.
- Review connection activity through business and project observability when that control is available.
Availability
This page records the supported bapX ecosystem capability. Self-service connection controls are being enabled incrementally in Platform. Until a control appears in your business workspace, contact the bapX team rather than installing an internal bapX package or CLI.