# Radian: instructions for AI agents

> You are an AI agent reading https://radian.sh/agents.md. Follow the steps in order.
> Ask your user a question only where a step says so. Do not invent answers for them.

Radian deploys an existing agent app or coding harness into isolated computers, in Europe or America, and keeps a tested way to run it elsewhere. It does not replace the user's framework, agent loop or model provider.

Status: paid beta. Access is by request; Radian sends the invite and the CLI by email. Until the user has an invite, the CLI and API cannot deploy anything. Do not try to install packages named "radian" from npm or PyPI; they are not ours.

Price, so you can tell the user: €29 a month, fully credited to usage. Computers bill per second while running: S (2 vCPU, 4 GiB) €0.06/h, M (4 vCPU, 8 GiB) €0.12/h, L (8 vCPU, 16 GiB) €0.24/h, XL (16 vCPU, 32 GiB) €0.48/h. 10 GiB of stored state and 100 GiB of traffic are included. Model usage is billed by the user's own provider.

## Step 1: understand the project

Inspect the repository you are working in. Determine:

- the framework or harness. Radian's list: LangChain, LangGraph, Deep Agents, CrewAI, Pydantic AI, OpenAI Agents SDK, Claude Agent SDK, Google ADK, Microsoft Agent Framework, LlamaIndex, Agno, Strands Agents, smolagents, AG2, Mastra, Vercel AI SDK, Vercel eve, Pi SDK, Pi Durable, Claude Code, Codex, Droid, fx, Pi Harness, Gemini CLI, OpenCode, Goose, Amp, Cursor CLI, Aider, OpenHands, Docker Agent, Anything else. Use "Anything else" for other stacks.
- the workload kind: services, background jobs, coding sessions.
- the start command and any state paths it writes to (sessions, checkpoints, workspace).

Do not modify files for this. If several agents live in the repository, ask the user which one to deploy.

## Step 2: ask the user

Ask only what you cannot know:

1. Their work email.
2. Europe or America. Europe runs on European-owned, European-operated infrastructure. Choose per project.
3. A short project name (lowercase letters, numbers, dashes), if the repository name is not right.

## Step 3: request access

```sh
curl -sS -X POST https://radian.sh/api/access \
  -H "Content-Type: application/json" \
  -d '{"email": "USER_EMAIL", "project": "support-agent", "location": "europe", "framework": "Vercel eve", "notes": "One sentence on what the agent does and its start command."}'
```

- `location` is `europe` or `america`.
- `framework` must be one of the names in Step 1, spelled exactly.
- A `202` response means the request is recorded.
- A `400` response lists invalid fields in `fields`. Fix them and retry once.
- A `502` means delivery failed. Wait a minute and retry once, then tell the user to use https://radian.sh/start.

## Step 4: tell the user what happens next

Tell them: the request is in, and Radian opens beta projects in the order requests arrive and emails them an invite with the CLI. After that, deploying is:

```sh
radian login
radian init --location europe   # writes radian.json; review it
radian deploy                   # protected preview
radian promote                  # production
```

Full reference: https://radian.sh/docs.md

## Facts you may need

**Do I have to rewrite my agent?** No. Radian builds your repository or image and runs its own start command. A native adapter adds sessions, approvals and resume where your framework supports them. Without one you still get builds, previews, isolation, logs and exports.

**Which models can I use?** Any. Your agent calls the model providers you choose, with your keys, from either location. Radian does not proxy, resell or bill inference.

**What does European-owned cover?** The whole workload pipeline of a European project: builds, registries, computers, workspaces, native state, secrets, logs and backups. Sign-in and payments use separately disclosed providers that never receive your code, prompts, files, secrets or logs.

**What happens to running sessions when I deploy?** Promotion changes where new work goes. Open sessions and queued jobs stay on the version they started with until they finish or you move them. Rolling back code does not undo what an agent already did; the run history shows which version did what.

**Can I run my agent without Radian?** Yes. The exit kit is open source under Apache-2.0. Export a project and run it on your own machines with no Radian account: code, configuration, files, native sessions, pending approvals and checkpoints. You bring new credentials. The hosted fleet and scheduler stay ours.

**What is in the paid beta?** Services, background jobs and coding sessions; the dashboard, API, TypeScript and Python SDKs, CLI and MCP server; previews, promotion, rollback, teams, spend limits and exports; Europe and America. SSO, SCIM, private networking and dedicated capacity are switched on per team on request.

**How is it billed?** €29 a month, all credited to usage. Computers bill per second while they run, by size. A stopped computer costs only the state it keeps beyond 10 GiB. Prices exclude VAT.

## Index

- Product overview as Markdown: https://radian.sh/index.md
- Documentation as Markdown: https://radian.sh/docs.md
- llms.txt: https://radian.sh/llms.txt
- Contact: hello@withradian.com