Install Jentic One Beta

Connect the Orgo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orgo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Forgo.ai%2Forgo" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Forgo.ai%2Forgo" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Orgo API.

Provision a cloud computer in a workspace with os, ram, cpu, disk_size_gb, gpu, and resolution, or from a template_ref

Drive a running computer through POST /api/v1/chat/completions, an OpenAI-shaped endpoint where the model clicks, types, and runs commands

Run apps on a computer as services with a command, port, env, and restart policy, then read their logs or restart them

Serve a computer's port at a public URL on orgo.dev or at a custom domain verified by DNS TXT record

GET STARTED

Start building with Orgo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Orgo API for, with concrete tasks.

★ Computer-use agent sandbox through Jentic

An AI agent that needs a real desktop to complete a task, such as using a web app with no API, can get one from Orgo. Through Jentic the agent searches for 'create a cloud computer', receives the Orgo createComputer operation with its input schema, and calls POST /api/computers with a workspace_id and name. It then sends the task to POST /api/v1/chat/completions with the computer_id and messages, and the model operates the computer until it answers.

Call POST /api/computers with workspace_id from GET /api/workspaces, name 'research-box', and os 'linux', then call POST /api/v1/chat/completions with that computer_id and a user message 'Open example.com and copy the pricing table'

Preview environments from GitHub

A developer wants each branch running somewhere reachable without managing a server. POST /api/computers/{id}/deploy-projects imports a GitHub repository by installation_id and repo_id, or a public repo_url, with framework detection for node, python, dockerfile, compose, or static. POST /api/computers/{id}/deploy-projects/{projectId}/deployments deploys the newest commit, GET /api/computers/{id}/deployments/{deploymentId}/logs streams the build log, and POST /api/computers/{id}/deployments/{deploymentId}/rollback restores an earlier release.

Call POST /api/computers/{id}/deploy-projects with repo_url 'https://github.com/owner/name', branch 'main', and port 3000, then read GET /api/computers/{id}/deployments/{deploymentId}/logs until the build finishes

Running and exposing apps on a computer

A long-running service such as a bot or dashboard needs to stay up and be reachable. POST /api/computers/{id}/services adds an app with name, command, port, restart, and env or secret_env, GET /api/computers/{id}/services/{serviceId}/logs returns its recent output, and POST /api/computers/{id}/public-urls serves its port at a public orgo.dev URL. POST /api/computers/{id}/domains adds a custom domain, checked with the verify operation.

Call POST /api/computers/{id}/services with name 'dash', command 'npm start', and port 3000, then POST /api/computers/{id}/public-urls with port 3000 and label 'team-dash'

Agent-run invoicing

An agent doing paid work for a client can bill for it. POST /api/v1/invoices creates and finalises an invoice with an amount in cents or line_items and a customer email or phone, and requires an Idempotency-Key header. It returns a Stripe payment page url; POST /api/v1/invoices/{id}/send emails it, GET /api/v1/invoices/{id} reads its status, and POST /api/v1/invoices/{id}/void cancels it if unpaid.

Call POST /api/v1/invoices with an Idempotency-Key UUID, description 'Website audit', amount 50000, and customer email 'client@example.com', then POST /api/v1/invoices/{id}/send

Key Endpoints

61 endpoints — the orgo api provisions cloud computers for ai agents: virtual desktops running linux, windows, macos, android, or ios that an agent can drive.

METHOD

PATH

DESCRIPTION

POST

/api/computers

Provision a cloud computer

GET

/api/computers

List cloud computers

POST

/api/v1/chat/completions

Run an agent on a computer

POST

/api/computers/{id}/services

Add an app to a computer

POST

/api/computers/{id}/public-urls

Make a public URL for a port

POST

/api/computers/{id}/deploy-projects

Import a GitHub repository and deploy it

POST

/api/computers/{id}/deployments/{deploymentId}/rollback

Roll back to an earlier deployment

GET

/api/templates/global

List curated templates

POST

/api/computers

Provision a cloud computer

GET

/api/computers

List cloud computers

POST

/api/v1/chat/completions

Run an agent on a computer

POST

/api/computers/{id}/services

Add an app to a computer

POST

/api/computers/{id}/public-urls

Make a public URL for a port

POST

/api/computers/{id}/deploy-projects

Import a GitHub repository and deploy it

POST

/api/computers/{id}/deployments/{deploymentId}/rollback

Roll back to an earlier deployment

GET

/api/templates/global

List curated templates

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Orgo by hand means sending your key as a bearer token, adding an Idempotency-Key header on creates and invoices, and stitching together computer, service, deploy, and chat-completion calls. Through Jentic you install once, import Orgo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Orgo puts the computer id in the URL path (/api/computers/{id}/...), so a rule can pin your agent to one computer and the operations you pick on it. You choose the operations it may call, so account-level ones like POST /api/keys, POST /api/v1/credits, or invoice creation are not included unless you add them.

Credential isolation

Your Orgo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a cloud computer' or 'deploy a GitHub repo to a computer', and Jentic returns the matching Orgo operation with its input schema so the agent sends the right fields without browsing the reference docs.

FAQs

Specific to using Orgo API through Jentic.

What authentication does the Orgo API use?

The Orgo API uses HTTP bearer auth per its OpenAPI spec: send an Orgo API key as `Authorization: Bearer <key>`. The spec applies it globally, with a few exceptions: GET /api/health and the agent signup at POST /api/v1/agents are open, and the support endpoints accept a key optionally. POST /api/v1/chat/completions also takes an optional x-anthropic-key header, and POST /api/v1/credits takes a Payment-Authorization header for MPP payments. Through Jentic your Orgo key is held by your own Jentic One instance.

Which operating systems can an Orgo computer run?

POST /api/computers takes an os of linux (the default), windows, macos, android, or ios, with ram choices from 4 to 64 GB, a cpu value in vCPU, an optional gpu on Linux, and a resolution such as 1280x720x24. macOS computers have a fixed 10 GB of RAM per the spec.

How does the Orgo chat completions endpoint work?

POST /api/v1/chat/completions follows the OpenAI chat completions format, plus a computer_id for a running computer. The model operates that computer, clicking, typing, and running commands, until it answers, and stream true returns chunks as it works. Because it is OpenAI-shaped, the OpenAI SDKs work against the base URL https://www.orgo.ai/api/v1.

What are the rate limits for the Orgo API?

The OpenAPI spec does not specify request rate limits; what an account can run is governed by its capacity, which GET /api/account/capacity reports. Check the Orgo documentation at https://docs.orgo.ai for current limits.

How do I give my agent a cloud computer through Jentic?

Search Jentic for 'create a cloud computer', load the createComputer operation, and call POST /api/computers with a workspace_id and name. Then search for 'run an agent on a computer' to load POST /api/v1/chat/completions and pass the new computer_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an Orgo MCP server?

You don't need an MCP server to give your agent Orgo. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the computer, deploy, and template operations it needs on demand rather than loading all of them into its context.

Can I limit what my agent is allowed to do with the Orgo API?

Yes. Write a rule that allows POST /api/v1/chat/completions and GET /api/computers/{id}/services/{serviceId}/logs for a single computer id. The agent can then operate that one computer and read its app logs, but cannot create computers, mint API keys, buy credits, or send invoices, and every call it makes is logged.

Orgo API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputehttp (bearer)61 EndpointsREST

For Agents

Provision Linux, Windows, macOS, Android, or iOS cloud computers, run and expose apps on them, deploy GitHub repos, and drive a computer with an OpenAI-compatible computer-use chat endpoint.

Use for: Create a Linux computer with 8 GB RAM in my workspace, Run a computer-use agent on my Orgo computer to fill in a web form, Expose port 3000 on my computer at a public URL, Deploy a GitHub repository to an Orgo computer

Not supported: Does not train or host AI models, store source code, or run serverless functions. Use for provisioning and operating cloud computers for AI agents only.

The Orgo API provisions cloud computers for AI agents: virtual desktops running Linux, Windows, macOS, Android, or iOS that an agent can drive. It creates computers in a workspace with a chosen RAM, vCPU, disk, GPU, and resolution or from a template, runs apps on them as managed services with logs and restarts, and serves their ports at public URLs or custom domains. Computers can deploy GitHub repositories with builds, rollbacks, and environment variables. An OpenAI-compatible chat completions endpoint sends a conversation to a model that operates a named computer by clicking, typing, and running commands, and the account side covers API keys, capacity, credits, and invoices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

54%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Orgo API to your agent

Capabilities

Start building with Orgo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Orgo API

Jentic AI Readiness Score

Orgo API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness