Jeriko API

The Jeriko daemon exposes an HTTP API, WebSocket endpoint, and Unix socket for inter-process communication. All endpoints return JSON with a consistent { ok, data, error } envelope.

Base URL

The daemon listens on 127.0.0.1:7741 by default. The port is configurable via the JERIKO_PORT environment variable or the --port flag.

Quick Start

# Check daemon health
curl http://127.0.0.1:7741/health

# Send a message to the agent
curl -X POST http://127.0.0.1:7741/agent/chat \
  -H "Authorization: Bearer $NODE_AUTH_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"message": "What time is it?"}'

Response Format

Every endpoint returns a JSON object with an ok boolean. On success, the result is in data. On failure, error contains a human-readable message and code contains a numeric status code.

{
  "ok": true,
  "data": {
    "response": "The current time is 3:42 PM.",
    "tokensIn": 128,
    "tokensOut": 24,
    "sessionId": "abc123"
  }
}

Endpoints

GroupBase PathDescription
Health/healthDaemon status and uptime
Agent/agentChat, streaming, session spawning
Sessions/sessionSession CRUD and history
Channels/channelTelegram, WhatsApp management
Connectors/connectorOAuth and API key integrations
Triggers/triggersCron, webhook, file, HTTP, email, once
Scheduler/schedulerCron task facade
Billing/billingPlans, checkout, portal, events
Shares/shareShareable session links
Webhooks/hooksInbound webhook receiver
OAuth/oauthOAuth authorization flow