Skip to content

Wabee Agent Core API (v1)

Wabee Agent Core API

Wabee Agent Core API enables developers to interact with an AI agent in a custom, secure and flexible manner through REST API calls.

One can build applications to interact with the agent API to complete a task using any of the Agents endpoints which allow for both text streaming and direct JSON response. The Memory endpoints are useful for managing the agent memory programatically. Moreover, the Metrics endpoints provide an interface for monitoring the underlying Agent in terms of latency, health, token consumption and much more.

Download OpenAPI description
Overview
License

Wabee License

Languages
Servers
Mock server

https://api.docs.wabee.ai/_mock/openapi/

Production server

https://<your_agent_uri>.wabee.ai/

Agent

Endpoints for interacting with the AI agent

Operations

Memory

Endpoints for managing agent memory

Observability

Endpoints for monitoring agent performance and logs

Operations

Sessions

Endpoints for managing agent sessions

Operations

Request

Retrieves the complete conversation history and metadata for a specific session.

The session data includes:

  • All messages exchanged between user and AI
  • Timestamps for each message
  • Additional context like reasoning steps for AI responses
  • Session metadata

Each message contains:

  • role: Either 'human' or 'ai'
  • content: The actual message text
  • timestamp: When the message was sent
  • additional_context: Extra information like reasoning steps (for AI messages)
Security
APIKeyHeader
Path
session_idstring(Session Id)required
curl -i -X GET \
  'https://api.docs.wabee.ai/_mock/openapi/core/v1/sessions/{session_id}' \
  -H 'x-wabee-access: YOUR_API_KEY_HERE'

Responses

Successful Response

Bodyapplication/json
session_idstring(Session Id)required

The ID of the session.

messagesArray of objects(Messages)required

The messages exchanged during the session.

messages[].​rolestring(Role)required

The role of the message sender. Can be either 'user' or 'assistant'.

Enum"human""ai"
messages[].​contentContent (string) or Content (object)(Content)required
Any of:

The content of the message.

string(Content)
messages[].​timestampnumber(Timestamp)required

The timestamp of the message in seconds since the Unix epoch.

messages[].​additional_contextArray of Additional Context (objects) or Additional Context (null)(Additional Context)
Any of:

Additional context for the message.

Response
application/json
{ "session_id": "VSkqDuv", "messages": [ {}, {} ] }

Request

Returns a paginated list of all available chat sessions.

The response includes:

  • List of session summaries
  • Pagination information
  • Total count of returned sessions

Each session summary contains:

  • session_id: Unique identifier for the session
  • checkpoint_id: Internal reference ID
  • short_name: Brief description based on first message

Use the query parameters to navigate through pages:

  • before: Get sessions before this session ID
  • limit: Number of sessions per page (1-50)

Sessions are ordered by most recent first. Empty sessions (no messages) are automatically filtered out.

Security
APIKeyHeader
Query
beforeBefore (string) or Before (null)(Before)
Any of:

Filter sessions before this session id

string(Before)
limitinteger(Limit)[ 1 .. 100 ]

Limit the number of sessions to return

Default 45
curl -i -X GET \
  'https://api.docs.wabee.ai/_mock/openapi/core/v1/sessions?before=string&limit=45' \
  -H 'x-wabee-access: YOUR_API_KEY_HERE'

Responses

Successful Response

Bodyapplication/json
sessionsArray of objects(Sessions)required

List of available sessions

sessions[].​session_idstring(Session Id)required

The ID of the session.

sessions[].​checkpoint_idstring(Checkpoint Id)required

The ID of the checkpoint.

sessions[].​short_namestring(Short Name)required

The short name of the session.

sessions[].​created_atstring(date-time)(Created At)required

The creation timestamp of the session in UTC.

Response
application/json
{ "sessions": [ {} ], "offset": "1efb5872-be2a-653c-8003-f96d250d9bed", "count": 1 }

Sub-Agents

Endpoints for managing sub-agents

Operations
Operations