Pre-release. Ophiolite runs today for design partners; public source and server image publication are in preparation.

Solutions

For developers and agent builders

Every tool has its own export, nothing is typed, and giving an agent access means giving it everything.

Why Ophiolite

One typed API with a published schema, a Python SDK and command line, generated types, and agents that reach the same API through MCP with scoped keys, budgets and plans a person approves.

What you can use

Available

Sign in once, stay signed in

Sign in through your organisation's sign-in provider or with an access key; one session policy applies to the browser, the SDK and applications.

Available

One typed API

Every scientific read and write goes through one versioned API with a published schema and generated Python and TypeScript types.

Available

Everything the browser does is scriptable

The Workspace is an ordinary client of the public API, so sharing, access and publication can be done from code.

Available

Python SDK, command line and templates

The ophiolite package reads exact versions into DataFrames and publishes results; templates cover notebooks, scripts, applications and agents.

  • Preview (0.x) release; Windows is not yet qualified
Available

Agents that act within your rules

A remote MCP endpoint and scoped agent keys with budgets; every change an agent makes needs a plan you approved.

  • Assistant sign-in against your own sign-in provider and automatic assistant approvals are not yet available
Available

Run code inside your boundary

Agents and long jobs run in containers with no network, a read-only file system and resource limits.

  • No GPU or distributed scheduling
Partial

Public conformance suites

Offline, server and agent conformance tasks anyone can run, and a nightly run against a deployment.

  • A model-driven agent test over MCP is not yet part of the suite
Partial

Apache-2.0 foundation

Apache-2.0 for project-owned code, source publication in preparation; a release-only candidate passes every gate privately.

  • Source publication in preparation; the source is not yet public

A day in the work

  1. Start from the Python application template in its synthetic mode.
  2. Sign in against a real deployment and read exact versions.
  3. Give an assistant a key with a small budget; approve its plans in the Workspace.
  4. Run the conformance tasks against your deployment.

See for yourself

The developer hub has the SDK sample quoted from the SDK itself, the API reference and the conformance commands.