How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SOJO Planning Assistant (Victoria) API

The HTTP surface for Victoria, the SOJO Planning Assistant — a LangGraph-backed agent over Sojo's production and machine-telemetry data. Publishes a public OpenAPI 3.0.3 describing non-streaming orchestration, SSE streaming chat, conversation CRUD/export, image upload and health/readiness probes, and serves a Model Context Protocol streamable-HTTP endpoint at /mcp for Claude Desktop and ChatGPT clients. Authenticated routes take a Stytch session JWT.

This API exposes 10 operations across 8 paths, organized into 4 resource areas. It is described by OpenAPI 3.0.3, at version langgraph-production.

Requests are made against 2 base URLs: https://victoria-agent.sojoshield.com, https://victoria-agent.sojoshield.dev.

10 operations 8 paths 0 schemas 1 DELETE5 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
langgraph-production
Base URL
https://victoria-agent.sojoshield.com
Authentication
HTTP Bearer
Resource Areas
4

Authentication & Security 1

SOJO Planning Assistant (Victoria) API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

  • BearerAuth — Stytch session JWT. Pass as 'Authorization: Bearer '.

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 1 DELETE, 5 GET, 1 PATCH, 3 POST. They span 4 resource areas: Chat, Conversations, Files, Health. Each is listed below with its method, path, parameters, and response codes.

Chat 2

Orchestration / streaming chat

POST
/orchestrate
Run a (non-streaming) orchestration turn
body → 200400401422503
POST
/api/chat
Streaming chat (Server-Sent Events)
body → 200400401
Conversations 5

Chat-history list/read/rename/delete (requires AGENTPERSISTENCEENABLED; 404 when the feature is off)

GET
/api/chat/conversations
List the caller's conversations (paginated)
2 params → 200401404422
GET
/api/chat/conversation/{session_id}
Get the full message thread
1 param → 200401404
PATCH
/api/chat/conversation/{session_id}
Rename the conversation
1 param body → 200401404422
DELETE
/api/chat/conversation/{session_id}
Delete the conversation (soft)
1 param → 204401404
GET
/api/chat/conversation/export/{session_id}
Export the thread as a debug snapshot
1 param → 200401404
Files 1

Image upload (files are uploaded via Shield, then referenced by S3 key)

POST
/upload-image
Upload raw image bytes
body → 200400
Health 2

Health probe

GET
/health
Health check (load balancers)
→ 200503
GET
/ready
Readiness probe (fail-closed on persistence)
→ 200503

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sojo-industries-victoria-agent-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of SOJO Planning Assistant (Victoria) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.