Product / Agents

Agents

Agents reach Ophiolite over a remote MCP endpoint with a scoped key and a budget. Every change they want to make is a plan you approve.

For teams that want assistants and agents to help without handing them the keys.

Available Agents that act within your rules
Available Run code inside your boundary

Key features

Remote MCP: One endpoint for MCP clients; the tools are exactly the agent's reach.
Scoped keys: An agent acts for you with narrower permissions and an expiry.
Budgets: Daily limits on runs and publications.
Approved plans: Configure, start and publish need a plan for exactly that request.
One assistant per sign-in: An assistant using your own sign-in asks you first.
Recorded executions: Every execution names the agent, the operation and its plan.

How it works

Register an agent with its reach, budget and expiry.
It proposes the exact request it wants to make.
You approve the plan; only that request can run.

Technical details

Plans are hashes of the exact request; a changed request or another agent cannot use an approved plan. Approval happens in the Workspace, never over MCP.

Use cases

An assistant in your notebook

Let it propose calculations; approve the ones you want.

Scheduled checks

An agent with a small budget checks new data every day.

Audit

See every agent execution with its plan and approval.

Not yet, and not planned

Agents that act within your rules: Assistant sign-in against your own sign-in provider and automatic assistant approvals are not yet available
Run code inside your boundary: No GPU or distributed scheduling

Not planned: suite-wide petrel or techlog replacement; a general application builder or marketplace; universal format conversion.