Docs

Install the Radius package to unlock Radius-specific integrations in Pi, as well as to use the only Pi-native gateway.

pi install npm:@earendil-works/radius-pi

What it includes

Depending on the version you install, the package can expose:

• Radius provider integration for Pi models
• Radius routing controls and rewrite tools
• Google Workspace connect and token delegation helpers
• Radius-backed web tools such as search and fetch
• Radius-backed image generation

Why install it

Without the package, you can still authenticate against Radius and use the hosted gateway where supported.

With the package, Pi can expose the Radius-specific commands, local integration flows, and tool surfaces that make those account capabilities discoverable.

The important model is that Radius is primarily one bundled extension package. The core Radius extension is the required entry point, and the other capabilities are usually turned on from inside Pi via slash commands that add or enable the corresponding bundled Radius features for you.

Radius provider

The Radius extension is the main bundled extension and the one you actually need first.

It connects Pi to the Radius gateway, registers the models returned by Radius, and adds the /radius command.

That command lets you configure routing for the current model, prefer or force a specific upstream provider, clear back to automatic routing, and refresh Radius models.

In practice, this is the core extension that makes Radius feel native inside Pi, and the other Radius add-ons build on top of it rather than being entirely separate installs.

Google Workspace

Google Workspace support is bundled with the Radius package and exposed through the /google-workspaces command.

That command adds or enables the needed Radius-backed integration flow for you, then handles the local browser-based OAuth flow for connecting a Google account through Radius.

It opens the sign-in flow, receives the localhost callback, and stores the resulting delegated tokens locally so Pi can use them later.

Use this when you want Pi to work with Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, or Meet through Radius-mediated credentials. You can enable all for read only or read and write.

Image generation

Image generation support is bundled with the Radius package and can be surfaced from Pi through the Radius-provided command flow rather than as a totally separate install.

Once enabled, it exposes the image_generation tool through Radius-backed OpenRouter image generation.

This lets Pi treat image generation as a normal tool call while Radius handles the upstream request and account-backed billing.

Use it when you want image generation available from the same Radius account and gateway setup as your models.

Web search

Web search support is bundled with the Radius package and can be enabled from Pi through the Radius command surfaces.

Once enabled, it exposes Radius-backed search as a Pi tool.

Under the hood, Radius serves this through the Parallel API, so Pi can issue search work through the shared Radius web-tools path instead of needing separate local search provider setup.

The resulting usage is accounted for through your Radius account.

Use it when you want search to be centrally managed, billable through Radius credits, and available as part of a shared package loadout.

Web fetch

Web fetch support is bundled with the Radius package and can be enabled from Pi through the Radius command surfaces.

Once enabled, it exposes Radius-backed fetch as a Pi tool.

Like web search, Radius serves this through the Parallel API, so Pi can retrieve and process web content through the same bundled web-tools path.

It uses the same account, auth, and billing model as the rest of the Radius package.

Use it when you want Pi to fetch and read web content without separately wiring local fetch infrastructure.

Tool output rewriting and related Radius add-ons

Some Radius package features are less like standalone tools and more like behavior layers on top of Pi and the gateway, such as rewriting tool outputs or exposing additional Radius-specific commands.

These are still part of the same bundled Radius package model: install Radius once, then use Pi commands and loadout controls to enable the pieces you want.

That is the main reason to think of Radius as one installable distribution with multiple bundled capabilities, rather than a pile of unrelated extension installs.