Accessing your deployment

A dedicated Hindsight Enterprise deployment (private cloud, BYOC or on-premises) has its own URLs, sign-in and API keys, separate from Hindsight Cloud. This page shows where to find them and how to point the SDKs, the API and MCP clients at your deployment.

If your organization uses Hindsight Cloud with Enterprise features, nothing changes: use the standard Hindsight Cloud URLs and follow Getting Started.

Your deployment's URLs

Each dedicated deployment has three endpoints. The Hindsight team gives you the exact hostnames when your deployment is handed over.

Endpoint	Typical hostname	Used for
Console	https://ui.<your-deployment-domain>	The web console: memory banks, API keys, team, settings
API	https://api.<your-deployment-domain>	The REST API, the SDKs and the MCP server
Sign-in	https://auth.<your-deployment-domain>	The identity service that handles sign-in and SSO

For private cloud and BYOC deployments, Vectorize manages DNS and TLS certificates for these hostnames. For on-premises deployments, they live in your DNS with certificates from your own certificate authority.

If your deployment uses private networking, these hostnames resolve only inside your network, and your applications reach Hindsight through your private endpoint.

Examples use the Hindsight Cloud URLs

Code samples throughout these docs use the Hindsight Cloud endpoints (https://api.hindsight.vectorize.io and https://ui.hindsight.vectorize.io). Replace them with your deployment's API and console URLs.

Signing in

The Hindsight team creates your organization and invites its first owner. From there:

1. Open your console URL and sign in with the invitation you received.
2. As an owner, set up Single Sign-On so your team signs in with your identity provider. Members on your verified domain are provisioned automatically on first sign-in.
3. Optionally require MFA for everyone in the organization.
4. Invite anyone who isn't covered by SSO from the Team page. See Team Management for roles and permissions.

Creating an API key

API keys authenticate the SDKs, the REST API and MCP clients.

1. In your console, open API Keys. Only owners and admins can create keys.
2. Click Create API Key, give it a name and an expiration, and optionally restrict it to specific memory banks.
3. Click Create and copy the key; it is shown only once.

See API Keys for bank-scoped keys, rotation and programmatic key creation.

Pointing clients at your deployment

Pre-built integrations for agent frameworks and AI tools take the same two settings: your API key, and your deployment's API URL (usually HINDSIGHT_API_URL). For your own code:

Python

from hindsight_client import Hindsight

client = Hindsight(
    base_url="https://api.<your-deployment-domain>",
    api_key="your-api-key",
)

See the Python SDK guide.

TypeScript

import { HindsightClient } from '@vectorize-io/hindsight-client';

const client = new HindsightClient({
  baseUrl: 'https://api.<your-deployment-domain>',
  apiKey: 'your-api-key',
});

See the TypeScript SDK guide.

cURL

curl https://api.<your-deployment-domain>/v1/default/banks \
  -H "Authorization: Bearer your-api-key"

See cURL Examples and API Integration.

MCP

https://api.<your-deployment-domain>/mcp/YOUR_BANK/

MCP clients that support OAuth sign in through your deployment's sign-in page; others use an API key in the Authorization header. See MCP Integration.

Next steps

• Create your first memory bank and retain some memories.
• Review the security features available on your deployment.
• Raise questions or issues through Enterprise Support.