Security and network setup
Keep credentials on your server and understand the connection boundary.
Credential handling
Use HTTPS and a server-side Authorization header. Store keys in your deployment's secret manager. Redact headers from logs, traces and error reports. Do not place keys in URLs, client bundles, public repos or model prompts.
The docs site contains public documentation and a public schema. It has no customer data credentials, account session, authenticated request proxy or browser API-key input.
Network direction
Your app calls Sloe's public HTTPS API. If your organization restricts outbound traffic, coordinate access to the API hostname and, for MCP, the connector hostname and its authentication flow.
“Egress” means traffic leaving a system. Sloe uses Vercel-managed hosting and Neon-backed data access. No dedicated static outbound-IP configuration was established in the November 4 review. Do not use a Vercel web/DNS IP as an assumed fixed outbound IP for Sloe.
An API response to your request is different from Sloe proactively calling your system. This documentation does not promise webhooks, private networking, a dedicated gateway or push-based CRM delivery. If your architecture requires those, confirm the requirement with Sloe before designing around it.
Your application boundary
Authorize downstream users, constrain tool inputs and confirm license scope before exposing data outside your team. Treat source text as untrusted data rather than executable instructions. Read-only access to Sloe does not authorize writes in another system.