Restore an archived agent
Restore an archived agent, clears `archived_at` so it reappears in the workspace agents list. The reverse of `archive_agent`. No-op (still succeeds) if the agent isn't archived.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Path Parameters
Workspace slug (GET /me lists yours).
Agent slug within the workspace.
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/workspaces/string/agents/string/restore" \ -H "Content-Type: application/json" \ -d '{}'{
"property1": null,
"property2": null
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}List agents GET
List the agents you can access, each with its handle ('workspace-slug/agent-slug'), name, published status, active flag, and last-updated time. Archived agents are hidden by default (matching the app's agents list); pass include_archived: true to see them too (each carries an `archived` flag, so you can find one to restore_agent). Optionally scope to one workspace by slug. Call this to discover what exists before editing; every agent-scoped tool needs the exact handle.
Send the agent a text message and get its reply POST
Have a live text conversation with the agent, the headless equivalent of the Test panel. Send a `message`, get back the agent's `reply`, the `toolCalls` it ran, and turn `timing`. Multi-turn: pass the returned `conversationId` back to keep the same thread (the agent remembers prior turns and won't re-fire tools it already ran). Defaults to the latest draft so edits you just made are testable immediately, use this to iterate: edit the agent, talk to it, see how it responds, refine. Each turn runs the real agent loop (executing tools) and is billed like a Test-panel turn; the conversation shows up in the Transcripts dashboard.