API & SDK

The programmable interface to the QORIS control plane. Interact with agents, memory, orchestration, and governance through REST APIs and SDKs.

QORIS APIs provide access to reasoning and planning, memory as the system of record, execution coordination, and policy enforcement—all operating above models and tools in a model-agnostic architecture.

Quick Start

1

Authenticate

Obtain an API key from your QORIS account and include it in request headers for authentication.

2

Create or Register an Agent

Define an agent configuration or register an existing agent workflow with the control plane.

3

Read/Write Memory and Execute Tasks

Submit tasks, persist context to memory, and coordinate execution through the orchestration layer.

API Domains

Agents & Reasoning

Interface to the Thinking Agent OS for reasoning and planning operations.

  • Create or update agent definitions
  • Submit goals or tasks for reasoning
  • Retrieve plans and decisions

Enables agents to reason about tasks and form execution plans independently of underlying models.

Memory & Context

System of record for persistent context, decisions, and knowledge.

  • Write memory entries with scope
  • Read memory by agent or system scope
  • Retrieve context for a task

Provides persistent memory that operates independently of models and tools, enabling continuity across sessions.

Orchestration & Execution

Coordination layer for managing execution across agents and tools.

  • Trigger task execution
  • Monitor task state and progress
  • Handle retries and resumptions

Manages execution coordination, dependencies, and state transitions for reliable multi-step processes.

Governance & Policies

Constraints, approvals, and auditability for agent operations.

  • Define policy constraints
  • Configure approval checkpoints
  • Retrieve audit logs and traces

Enforces policies uniformly across all agents and operations, providing control and compliance at scale.

Examples

These examples demonstrate request patterns. Exact endpoints may vary by deployment.

Save a memory via MCP

POST https://mcp.qoris.ai/mcp/tools/call
Authorization: Bearer qoris_YOUR_API_KEY

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "save_memory",
    "arguments": {
      "content": "Customer prefers dark mode and weekly email digests",
      "agent_id": "customer-support-agent",
      "agent_name": "Customer Support Agent"
    }
  }
}

Retrieve workspace memories

POST https://mcp.qoris.ai/mcp/tools/call
Authorization: Bearer qoris_YOUR_API_KEY

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_memories",
    "arguments": {
      "limit": 50,
      "offset": 0
    }
  }
}

Response:
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "success": true,
    "memories": [
      {
        "memory_id": "uuid-123",
        "content": "Customer prefers dark mode...",
        "created_at": "2024-01-15T10:30:00Z",
        "agent_name": "Customer Support Agent"
      }
    ],
    "total": 127,
    "limit": 50,
    "offset": 0
  }
}

Update or delete a memory

POST https://mcp.qoris.ai/mcp/tools/call
Authorization: Bearer qoris_YOUR_API_KEY

// Update memory
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "update_memory",
    "arguments": {
      "memory_id": "uuid-123",
      "content": "Updated content here"
    }
  }
}

// Delete memory
{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "delete_memory",
    "arguments": {
      "memory_id": "uuid-123"
    }
  }
}

SDKs

SDKs wrap the same control plane primitives exposed through REST APIs, providing language-specific interfaces for agents, memory, orchestration, and governance. SDKs handle client initialization, authentication, request retries, and idempotency patterns, reducing boilerplate in application code.

Use SDKs when building applications that integrate deeply with QORIS, as they provide type safety, error handling, and convenience methods. For simple integrations or custom workflows, direct REST API usage offers more flexibility and control.

SDKs are being formalized; start with the REST API conventions described above. The API surface is designed to be consistent across SDK implementations, ensuring that patterns learned through REST translate directly to SDK usage.

Events & Webhooks

Receive real-time updates about execution progress, approval requests, and system events through webhooks. Configure webhook endpoints to be notified when tasks complete, when approvals are required, or when memory entries are created or updated.

Webhook support is planned for future releases, enabling event-driven integrations with external systems.