oorbital

Control infrastructurefor your AI ambitions.

Delegate valuable work to AI.
Retain authority over the outcome.

Read Oorbital without 3D.

Your browser does not have WebGL2 available. All the text, diagnostics and contact options are available in reading view.

Oorbital

Your next step.

This destination is reserved for the next build.
Intelligence · Example

Less repeated work.
The same care.

Oorbi keeps researching answers already approved by your team. Reusing those answers is an opportunity to reduce repeated work.

The suggested change leaves the £200 refund limit in place. It still needs testing before release.

A local example, not a measured performance or savings claim.
The AI Abundance Report

Preview from the supplied report introduction.

Understand the contract.
Then write the code.

Source-backed starting points for bringing Oorbital into your own application. Keep implementation responsibilities explicit.

All Insights rooms ↙
↓Choose a desk, or scroll to the reading list.
Insights

Documentation room

Find what you need.
Open it here.

Read and work without losing your place in the room.

2 of 2 resources

↙ Back to the office
Eight questions. A clearer next step.
oorbital

Take your time. Oorbi has the next question.

Your work, saved

Your diagnostic results.

Developer quick start

Keep your stack.
Add an execution boundary.

DOCUMENTATION / SDK QUICK START

Keep your stack.
Add an execution boundary.

An example from the Oorbital SDK documentation. The wrapper governs the action; your application still owns the tool implementation.

import { RuntimeClient, govern } from "@oorbital/sdk";import { executeRefund } from "./your-payments"; const runtime = new RuntimeClient({  credential: process.env.OORBITAL_RUNTIME_CREDENTIAL!}); const refund = govern({  client: runtime,  proposal: (paymentId: string, amount: number) => ({    agentId: "agt_...",    versionId: "agv_...",    functionKey: "payments.refund",    action: {      functionKey: "payments.refund",      target: { type: "payment", id: paymentId },      parameters: { amount, currency: "EUR" }    },    context: { customerTier: "standard" },    environment: "sandbox"  }),  argumentsFromEffectiveAction: (action, [paymentId]) => [    paymentId, Number(action.parameters.amount)  ]}, executeRefund); // Replace identifiers and your-payments with your own sandbox integration.
Source documentation ↗
01

Configure on the server.

Use a scoped Runtime credential. Replace sandbox identifiers and the payment implementation with your own integration. Never put credentials in browser code.

02

Use the effective action.

Map the authorised action back into tool arguments. A pending or refused proposal must not execute. A changed action without a mapping must fail closed.

03

Test more than the happy path.

Exercise approval, refusal, review, changed actions and an unavailable service. Preserve idempotency, the execution claim and the outcome record.

This website displays the example. It does not execute it or create a live connection.

Local interactive tool. Nothing is sent or executed.OORBITAL · INSIGHTS
Oorbital

Share a private copy

Share your results.

Choose who receives your results. Nothing is published online.

Open an email draft ↗

Your email app handles sending. This page does not send messages.