Enterprise setup

1. Define the workflow

Send your Oceanir contact the information needed to scope access:

• Your organization name, account owner, and email domain.
• Whether the team will use the app, REST API, MCP, or a combination.
• Expected analysis volume, depth, and number of users.
• Any requirements for retention, identity management, support, or data handling.

If you are evaluating Enterprise, contact Oceanir to arrange onboarding.

2. Confirm workspace access

Sign in with the account designated during onboarding. Confirm that the intended organization and member access are available before adding an integration.

Use your organization’s agreed roles and seats. If the workspace is missing or access looks incorrect, contact your workspace owner or Oceanir rather than creating a second subscription.

3. Choose an integration

REST API

Organizational and production integrations use organization-scoped keys with contracted limits. Keep these keys on your server. Follow authentication, then run the API quickstart.

MCP

MCP tool calls require approved Enterprise access and an OAuth token or scoped agent token. Follow client setup and MCP authentication. A REST API key is not an MCP agent token.

Confirm which account or organization pays for each integration before running a workload. MCP agent tokens currently use personal account billing.

4. Configure identity access

For SSO onboarding, provide your identity provider, organization domain, and administrator contact. Oceanir scopes the provider to your organization and verifies the domain before access is enabled.

SAML and OIDC are supported. Obtain your organization’s callback or ACS URL during setup and test sign-in with a designated account before rolling it out to the team.

SCIM is not a self-service setting. Discuss provisioning requirements with Oceanir during implementation review.

5. Validate before launch

• Confirm a team member can sign in and access the correct workspace.
• Run a representative image and review the result and credit usage.
• Check that invalid credentials and permission limits are handled by your integration.
• Record your support contact and the agreed process for rotating credentials.

Retention, regional deployment, dedicated capacity, audit exports, and service commitments depend on your agreement. Confirm those settings with Oceanir before relying on them in production.

Get help

Email enterprise@oceanir.ai with your organization, the affected workflow, and a request ID if available. Do not include API keys or access tokens.