EIGNN
EIGENN // API REFERENCE

System Interface for Intelligence Infrastructure.

Structured access. Controlled interaction.

VERSION
v1.0
PROTOCOL
REST + JSON
AUTH
Bearer Token

Interface Design

Interfaces must be structured.
Clarity defines usability.
Complex systems require simple access.

The Eigenn API exposes the full intelligence infrastructure through a consistent, minimal interface. Every endpoint maps to a system capability — nothing more, nothing less.

System Architecture

How the API Interacts with the System

Each API namespace maps directly to a system layer. Requests enter through a unified gateway and are routed to the appropriate intelligence subsystem.

Entry Point
API Gateway
api.eigenn.com/v1
Auth
Rate Limit
Versioning
Data Systems/data/*Ingest, query, and structure operational data across sources.
Decision Systems/decision/*Evaluate inputs and generate structured decision outputs.
Model Systems/model/*Invoke, configure, and observe intelligence model layers.
Integration Systems/integration/*Manage platform connections, webhooks, and event dispatch.
Base URLhttps://api.eigenn.com/v1

Endpoint Categories

Four System Namespaces

#CategoryEndpointsCount
01
Data Endpoints
/data/*
Ingest raw data, query structured datasets, manage data sources, and retrieve the normalised semantic layer.
POST/data/ingest
GET/data/query
GET/data/sources
DELETE/data/source/:id
4
02
Decision Endpoints
/decision/*
Submit input for evaluation, retrieve decision outputs, access decision history, and configure decision graphs.
POST/decision/evaluate
GET/decision/:id
GET/decision/history
PUT/decision/graph
4
03
Model Endpoints
/model/*
Invoke models directly, retrieve inference outputs, configure model parameters, and monitor model performance.
POST/model/infer
GET/model/status
PUT/model/config
GET/model/metrics
4
04
Integration Endpoints
/integration/*
Manage external connections, configure webhooks, subscribe to system events, and monitor integration health.
POST/integration/connect
POST/integration/webhook
GET/integration/events
DELETE/integration/:id
4
Total endpoints16

Endpoint Detail

Featured Endpoints

Select an endpoint to view its parameters, request schema, and response structure.

Evaluates structured input and returns a system-generated decision output with confidence score and audit metadata.

Parameters
inputobjectrequired
Input payload to evaluate. Schema is domain-defined.
contextobject
Optional operational context — enriches decision accuracy.
asyncboolean
If true, returns a job ID instead of an immediate result.
Request body
// POST /decision/evaluate
{
  "input"  : {
    "domain": "risk_assessment",
    "entity": "account_88421",
    "data":   {"exposure": 142000, "region": "APAC"}
  },
  "context": "quarterly_review"
}
Response
// 200 OK
{
  "decision":    "approved",
  "confidence":  0.92,
  "rationale":  [
    "Exposure within approved threshold",
    "Region risk score nominal"
  ],
  "audit_id":   "dec_a91f3c",
  "latency_ms":118
}

Request / Response

Standard Structure

Every endpoint follows the same request and response schema. Consistency is architectural — not stylistic.

Request Schema
All requests require a Bearer token in the Authorization header. The body must be valid JSON with Content-Type: application/json.
// Standard request envelope
{
  "Authorization": "Bearer $TOKEN",
  "Content-Type": "application/json",

  // Body
  "input": {
    "data": "...",
    "context": {},
    "options": {}
  }
}
Success Response
Successful responses return HTTP 200 with a JSON body. All responses include a request_id for traceability and a timestamp in ISO 8601 format.
// Standard success envelope
{
  "status": "ok",
  "request_id": "req_01j9k...",
  "timestamp": "2026-04-11T09:14:00Z",

  // Payload — varies by endpoint
  "output": {
    "decision": "approved",
    "confidence": 0.92,
    "reasoning": "..."
  }
}
Error Response
Errors return a non-2xx HTTP status. The body follows the same envelope structure with an error object describing the fault.
// Standard error envelope
{
  "status": "error",
  "request_id": "req_01j9k...",
  "timestamp": "2026-04-11T09:14:00Z",

  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Required field missing: input.data",
    "field": "input.data"
  }
}

HTTP Status Codes

CodeLabelDescription
400Bad RequestMalformed JSON or missing required fields.
401UnauthorizedMissing or invalid Bearer token.
403ForbiddenToken valid but lacks required scope.
404Not FoundResource does not exist at the specified identifier.
422Unprocessable EntityInput passes schema validation but is semantically invalid.
429Rate LimitedRequest count exceeded. Retry after the indicated window.
500Internal ErrorUnexpected server fault. Include request_id when reporting.

Integration Flow

Request Lifecycle

A request enters the system at a single point and traverses a deterministic path before returning structured output.

01
Client
Your Application
Any HTTP client — SDK, curl, or programmatic request. Attach Bearer token and JSON body.
02
API Gateway
api.eigenn.com/v1
Validates authentication, enforces rate limits, routes to the correct subsystem.
03
Intelligence Layer
Eigenn Core Systems
Data ingestion, model inference, decision graph evaluation — all processed internally.
04
Response
Structured Output
Normalised JSON envelope returned to the client. Consistent schema across all endpoints.

System Constraints

Latency Target
< 200ms p99
Auth Method
Bearer Token
Max Payload
10 MB
Rate Limit
1 000 req/min
Retry Policy
Exp. backoff

Developer Interface

Interfaces expose systems.
Structure defines usability.
The API is the architecture.

The Eigenn API is the boundary between your system and the intelligence substrate. Every endpoint is a deliberate surface — no more, no less.

Eigenn // API Reference v1.0