SUPPORT

Find the right path for the issue.

Start with documentation for integration questions. Email support@octopusos.ai for general help. Production customers should use the named operational contacts in their agreement for service incidents and environment-specific escalation.

01Docsintegration and API guidance

02Statusthrough agreed operations channels

03Supportsupport@octopusos.ai

04Contextrequest ID speeds investigation

Developer documentation

Use the developer documentation for API shape, authentication patterns, streaming and common integration work. Confirm environment-specific settings with your workspace owner.

Base URL and SDK configurationExpand details
This is part of Developer documentation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Authentication and request patternsExpand details
This is part of Developer documentation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Streaming and structured outputsExpand details
This is part of Developer documentation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Routing aliases and error handlingExpand details
This is part of Developer documentation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Service status

There is no public status URL asserted on this page. Production customers receive service notices and incident updates through the operational channel agreed for their environment.

Check the agreed customer operations channelExpand details
This is part of Service status. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Include region, environment and observed timeExpand details
This is part of Service status. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Distinguish provider errors from router errors when possibleExpand details
This is part of Service status. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Follow incident instructions issued for your serviceExpand details
This is part of Service status. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Customer support

Email support@octopusos.ai for account, access and general service help. Customers with a named service desk or incident channel should continue to use that path for authorised, environment-specific support.

Identify the affected workspace and environmentExpand details
This is part of Customer support. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Provide a request ID without exposing credentialsExpand details
This is part of Customer support. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Describe expected and observed behaviourExpand details
This is part of Customer support. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Never include API keys, tokens or provider secretsExpand details
This is part of Customer support. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Response expectations

Support hours, severity definitions, escalation and response targets are those stated in the applicable agreement. This page does not create or expand an SLA.

Use the contractual severity process for incidentsExpand details
This is part of Response expectations. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Mark suspected credential exposure clearlyExpand details
This is part of Response expectations. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Preserve timestamps and relevant diagnostic evidenceExpand details
This is part of Response expectations. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Refer to the agreement for response commitmentsExpand details
This is part of Response expectations. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

Working on an integration question?

The documentation is the fastest starting point for API and SDK guidance.

Open developer docs