Radioso documentation

Grounded answers, traceable citations, and workspace-scoped controls for teams that need to defend what their assistants say.

Run locally in 5 minutes

The intended local path is the bootstrap script at the repo root. It prepares `.env`, starts Postgres, the backend, the worker, and the frontend, then waits until the stack is healthy.

./run-dev.sh

API first success

Reach first success with plain HTTP or the TypeScript SDK: create a session, reveal the workspace token, upload content, and ask one grounded question.

1import { createRadiosoClient } from '@radioso/typescript-sdk'
2 
3// baseUrl defaults to https://api.radioso.ai. Set it to
4// https://api-us.radioso.ai for the US instance, or to your own
5// origin when you self-host. A token only works against the
6// instance that issued it.
7const client = createRadiosoClient({
8  apiToken: process.env.RADIOSO_API_TOKEN!,
9})
10 
11const response = await client.chat.create({
12  message: 'What does the FAQ say about uploaded content?',
13  stream: false,
14})
15 
16console.log(response.answer)

Authentication

Radioso supports multiple access patterns depending on whether you are using the product UI, the developer API, or the public embed flow.

Authorization: Bearer YOUR_API_KEY

Grounded answers

Grounding is a product contract in Radioso, not a marketing flourish. Retrieval settings, citations, and unsupported-answer behavior exist so you can shape and inspect answer quality deliberately.