How Resia fits together
Resia separates what a conversation should do from each time it happens. You define an agent once, then start as many conversations with it as you need.
| You define | Each time it runs | Read more |
|---|---|---|
| Call Agent: instructions and settings for a phone conversation | Call: one attempt to place or answer a phone call | Call Agents, Calls |
| Chat Agent: instructions and settings for a text conversation | Chat: one text-message or web conversation | Chats |
| Orchestration Agent: a multi-step task that can call, text, and wait | Orchestration run: one execution of that task, over minutes or days | Orchestration Agents |
Everything belongs to your organization: agents, calls, chats, runs, live sessions, phone numbers, API keys, and the prepaid balance that pays for them.
The parts of Resia
Resia has two APIs. Both use the same API keys and the same prepaid balance.
| Part | What it is | Read more |
|---|---|---|
| REST API | HTTPS requests under https://api.resia.ai/v1. You create agents, start calls, chats, and runs, manage phone numbers, and read results. |
API Reference |
| Agents | The Call Agents, Chat Agents, and Orchestration Agents in the table above. Resia runs each conversation for you. | Call Agents |
| Phone numbers | The numbers that your agents call from, answer, and text on. | Phone numbers |
| Fullplex API (the Live API) | A WebSocket that carries live voice between your server and Fullplex, Resia's full-duplex voice service. | Live API |
Choose the part by where the conversation happens:
| Where the person talks | What you use |
|---|---|
| On a phone call | A Call Agent and a phone number, through the REST API. |
| In a text message or a web chat | A Chat Agent, through the REST API. |
| In your web app or mobile app, by voice | Your server connects to the Fullplex API. |
Your server opens a WebSocket to wss://api.resia.ai/v1/live/sessions with a Resia API key. Keep that key on the server. The web app or mobile app sends audio through your server and plays the speech that comes back. It needs no agent and no phone number. Signed-in organization members can use a portal ID token in a browser. See Connect a live session.
A Call Agent can also run its phone calls on Fullplex. See Fullplex on phone calls.
Inputs, instructions, and analysis
Every agent has the same three parts:
input_schema: a JSON Schema (draft 2020-12) for the values each conversation receives, such as a patient's name or an appointment date. Instructions refer to these values as$nameor${name}.instructions: what the agent should say and do.analysis_promptandanalysis_schema: how Resia turns the finished conversation into a structuredanalysisobject, such as{"confirmed": true, "new_time": "3:30 PM"}.
Because the result is structured, your software can act on it directly without parsing transcripts.
Review and versions
When you create an agent or change its instructions, Resia saves a new version. Resia may review a new version before it runs. While it waits, the previous approved version keeps running, so an edit never takes a working agent offline.
Read review_status (pending_review or approved) and is_active on the agent to see where it stands. You never manage version numbers yourself.
Directions
- Outbound: you start the conversation with an API request:
POST /v1/calls,POST /v1/call-batches,POST /v1/chats, orPOST /v1/orchestration-runs. - Inbound: a person calls or texts one of your Resia phone numbers. The agent assigned to that number answers. You assign agents with
PATCH /v1/phone-numbers/{phone_number}.
Getting results
Every call, chat, and run has an ID. You can:
- Poll it with a
GETrequest until it reaches a final status. - Receive a webhook when it ends. See Webhooks.
Both give you the same record.
A live session works differently. Your application receives the speech and the transcripts as events while the session runs. After the session, read its record, its charge, and its recording with GET requests under /v1/live/. See Session records and voices.
Tags
A tag is your own key and value on a record, such as {"team": "billing"}. Use tags to group records and to filter lists. See Tags.
Active counts and list order
The agent lists return active_call_count, active_run_count, or active_chat_count for each agent.
Zero means no active record. A missing count means Resia could not count it for this response.
The Agents page shows these counts. Its tabs are Orchestration Agents, Call Agents, and Chat Agents; Call Agents opens first.
- A call counts from when it starts dialing until Resia records its end, for at most two hours. A queued batch call does not count.
- A run counts in
queued,running, orwaiting. - A chat counts in
pending,active, orpost_processing.
The call count can lag behind the end of a call until Resia records its end.
The agent, call, run, chat, tool, database, and phone-number lists accept sort and order.
The API reference lists the allowed fields for each route. order accepts asc or desc; the default is desc.
Without sort, a list keeps its default order and cursor.
With sort, missing values come last in either direction. IDs decide the order of equal values.
created_at uses the creation timestamp. An agent's submitted_at uses the time of its newest version.
Use each next_cursor with the same sort, order, and filters. A cursor with a different sort or order returns 422.
Treat the cursor as opaque text. It retains the last value and ID, so an archived last record does not block the next page.
A record whose value changes can move between pages.
A run duration sort uses one server time across all its pages. A run that ends later uses that saved time as its end limit.
A run whose start is absent or later than that time has no duration value for that page sequence.
The portal still shows current durations. Their displayed order can differ from the fixed order as time passes.
A call duration sort has no fixed time. It uses the duration from Resia's latest read of each call, so a call can move while you page. Deduplicate pages by id.
Refresh duration order retains the direction and replaces all loaded pages with a fresh first page.
An explicit Calls sort stops automatic list refresh. Refresh sorted calls retains the direction and replaces all loaded pages. The default Calls list still refreshes while a visible call is in flight. Open call details keep their own refresh.

