Intelligence APIs¶
Why This Exists¶
This document defines API responsibilities for the Intelligence Domain.
It does not define implementation code or final OpenAPI specifications. Final OpenAPI specs come later.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Clear API responsibilities allow Algosure to expose intelligence capabilities safely to UX, workflows, Digital Professionals, and other domains.
API Groups¶
| API group | Responsibilities | Example endpoints |
|---|---|---|
| Intelligence Session API | Start, inspect, and close reasoning sessions. | POST /intelligence/sessions, GET /intelligence/sessions/{sessionId} |
| AI Agent Registry API | Register, update, suspend, and inspect agents. | POST /intelligence/agents, GET /intelligence/agents/{agentId} |
| Digital Professional Runtime API | Inspect and route runtime assignments. | GET /intelligence/digital-professionals, POST /intelligence/routing |
| Organization Context API | Load Organization context packages for reasoning. | POST /intelligence/context/organization/{organizationId} |
| Reasoning API | Execute approved reasoning patterns. | POST /intelligence/reasoning |
| Confidence API | Assess and retrieve confidence scores. | POST /intelligence/confidence, GET /intelligence/confidence/{assessmentId} |
| Explainability API | Store and retrieve explanations. | GET /intelligence/explanations/{explanationId} |
| Guardrail API | Evaluate approval and automation guardrails. | POST /intelligence/guardrails/evaluate |
| AI Memory API | Store and retrieve intelligence memory records. | POST /intelligence/memory, GET /intelligence/memory?organizationId= |
| Execution Coordination API | Request governed workflow execution. | POST /intelligence/execution-requests |
| Audit API | Query intelligence audit records. | GET /intelligence/audit?correlationId= |
API Responsibility Principles¶
- APIs must enforce Organization context where customer-bound.
- APIs must not mutate Organization-owned facts directly.
- APIs must record audit events for intelligence actions.
- APIs must expose confidence and explainability where outputs are customer-facing.
- APIs must respect human approval guardrails before execution.
API Boundary Diagram¶
flowchart LR
UX[UX and Digital Professionals]
API[Intelligence APIs]
Domain[Intelligence Domain]
Org[Organization APIs]
Execution[Procurement Execution Engine]
Events[Event Mesh]
UX --> API
API --> Domain
Domain --> Org
Domain --> Execution
Domain --> Events