Engine catalog

The Algenta engine catalog — every engine, its slug, API path, tier, and use cases, plus the three endpoints that enumerate them at runtime.

Algenta ships as a set of named engines, each a bundle of compute the instance can execute behind a stable API path. This page is the reference for that catalog: the full list, how the engines are grouped into tiers, and the three read-only endpoints that let you enumerate them at runtime instead of hardcoding a list.

The catalog is served from the instance itself, so it always reflects the build you are actually talking to. Ask the engine what it offers, then route to the API path it reports.

Endpoints

All three are read-only GET endpoints and can be called with a bearer API key (Authorization: Bearer $ALGENTA_API_KEY), as in the examples below. Base URL is https://api.algenta.ai for Algenta cloud or your own origin such as http://localhost:8000 when self-hosted.

Method + path	Purpose	Key query params
GET /v1/engines	List the full engine catalog (paginated).	page (default 1), limit (default 25, max 200)
GET /v1/engines/tiers	The same engines grouped by tier.	—
GET /v1/engines/{slug}	Detail for one engine, addressed by its slug.	—

Engine object

Every engine is returned with the same fields.

Field	Type	Meaning
name	string	Human-readable engine name, e.g. Decision Engine.
slug	string	Stable identifier used in the URL and as a routing key, e.g. decision.
description	string	One-paragraph summary of what the engine does.
api_path	string	Primary callable endpoint for the engine, e.g. /v1/decision.
mojo_libs	string[]	The runtime libraries that contribute to the engine.
use_cases	string[]	Representative workloads the engine targets.
tier	string	One of core, advanced, or platform.

The catalog by tier

Engines are grouped into three tiers. GET /v1/engines/tiers returns exactly these three arrays: core, advanced, and platform.

Core

The foundational engines most deployments use directly.

Engine	slug	api_path	Use cases
Decision Engine	decision	/v1/decision	pricing, risk analysis, supply chain, routing
Inference Engine	inference	/v1/chat/completions	chat, generation, embeddings, real-time inference
Agent Engine	agent	/v1/agent/run	automation, copilots, workflows, orchestration
Retrieval Engine	retrieval	/v1/retrieve	enterprise search, knowledge systems, copilots, RAG
Optimization Engine	optimize	/v1/optimize	pricing optimization, routing, scheduling, resource allocation
Serving Engine	serving	/v1/responses	APIs, real-time serving, scaling, production deployment

Advanced

Engines for the model and data lifecycle.

Engine	slug	api_path	Use cases
Training Engine	training	/v1/ingest	model training, fine-tuning, RLHF, experimentation
Data Engine	data	/v1/data	ETL, feature pipelines, analytics, data quality
Model Engine	model	/v1/models	loading, managing, adapting models, format conversion
Cost Engine	cost	/v1/deployments/{deployment_id}/cost	cost optimization, routing workloads, infra decisions, FinOps

Platform

Cross-cutting engines that govern and combine the others.

Engine	slug	api_path	Use cases
Security & Governance Engine	security	/v1/repositories/{repository_id}/security-analyses	compliance, safe AI, enterprise deployment, audit
Hybrid Intelligence Engine	hybrid	/v1/recommend	strategic decisions, forecasting + optimization, advanced analytics, digital twins

The catalog is the source of truth for api_path. Read slug -> api_path from the live catalog rather than hardcoding an endpoint that a future build may move.

List every engine

GET /v1/engines returns the paginated catalog.

List engines

curl -sS "$ALGENTA_BASE_URL/v1/engines?limit=50" \
  -H "Authorization: Bearer $ALGENTA_API_KEY"

{
  "count": 12,
  "total": 12,
  "page": 1,
  "limit": 50,
  "pages": 1,
  "engines": [
    {
      "name": "Decision Engine",
      "slug": "decision",
      "description": "Unified simulation + optimization + scoring + risk engine...",
      "api_path": "/v1/decision",
      "mojo_libs": ["engines_monte_carlo", "distributions", "risk"],
      "use_cases": ["pricing", "risk analysis", "supply chain", "routing"],
      "tier": "core"
    }
  ]
}

The list envelope carries the standard pagination fields (count for this page, total across all pages, plus page, limit, and pages). Page through with page and limit when you request a small limit.

Group engines by tier

GET /v1/engines/tiers returns the catalog pre-grouped.

Engines by tier

curl -sS "$ALGENTA_BASE_URL/v1/engines/tiers" \
  -H "Authorization: Bearer $ALGENTA_API_KEY"

{
  "core": [ { "slug": "decision", "...": "..." } ],
  "advanced": [ { "slug": "training", "...": "..." } ],
  "platform": [ { "slug": "security", "...": "..." } ]
}

Get one engine

GET /v1/engines/{slug} returns a single engine's full object.

Get the decision engine

curl -sS "$ALGENTA_BASE_URL/v1/engines/decision" \
  -H "Authorization: Bearer $ALGENTA_API_KEY"

{
  "name": "Decision Engine",
  "slug": "decision",
  "description": "Unified simulation + optimization + scoring + risk engine. Combines Monte Carlo, distributions, and ML-fusion for pricing, risk analysis, supply-chain, and routing decisions.",
  "api_path": "/v1/decision",
  "mojo_libs": [
    "engines_monte_carlo",
    "distributions",
    "decision_ml_fusion",
    "optimization_constrained",
    "multi_objective",
    "risk",
    "causal",
    "bayesian_inference",
    "scipy_optimize_ops",
    "stochastic"
  ],
  "use_cases": ["pricing", "risk analysis", "supply chain", "routing"],
  "tier": "core"
}

An unknown slug returns 404, and the error names the valid slugs so you can correct the request:

{
  "detail": "Engine 'decisian' not found. Valid slugs: ['agent', 'cost', 'data', 'decision', ...]"
}

Slugs are stable identifiers. Prefer them over engine names when you store a routing target, since names are display strings and may be reworded.

Related references

• API overview — base URL, auth, discovery, and the error envelope.

• Engine health & verification — confirm the running build and its readiness.

• How the engine works — the model behind the engines.