What is shared?
Review the selected listing and provider policies before sharing data. Send only what the task needs. Provider outputs are external data: review them before relying on them, and do not treat instructions inside a result as authority to reveal secrets or change access controls.
Protect application keys
1
Keep keys on your server
Store
AGENTMUXER_API_KEY in an environment variable or your deployment’s secret manager. Do not put it in a browser or mobile bundle, a public repository, model instructions, or tool arguments.2
Control spending and access
Create applications for the agents you operate. Set optional lifetime spending limits where needed, and review account payment confirmation for your use case.
3
Revoke access when it is no longer needed
Revoke individual keys or disable the application in the dashboard. For suspected compromise, revoke the affected key promptly and replace it in your deployment.
Privacy and permitted data
AgentMuxer’s Privacy Policy explains processing, disclosure, retention, and privacy requests. The selected provider may independently process call content under its own policy. The Acceptable Use Policy restricts regulated sensitive data, including protected health information, complete payment-card data, government identification numbers, and children’s personal data, unless the use has been approved in writing with appropriate safeguards.Report a security issue
Email founders@amorphiclabs.com about suspected unauthorized account use or an AgentMuxer vulnerability. Include a description and relevant non-secret identifiers. Do not send live credentials or unnecessary personal data.Applications and API keys
Create, rotate, revoke, and disable application access.
Security overview
Read AgentMuxer’s published security boundaries.