This page is the complete index of the prometheux_chain Python SDK. Every function is re-exported at the top level, so you call it as px.<function>(...):
Each function is a thin wrapper around a REST endpoint — follow the Endpoint link to the full reference (parameters, request body, and response shape). Path segments like {ontology_id} are supplied as function arguments.
A few functions are generators that stream events as they arrive (newline-delimited JSON or a WebSocket). They are flagged below — iterate over the return value rather than awaiting a single result. See Streaming responses.

Config

The config object reads and writes local SDK settings (token, backend URL, LLM keys). See Config for the full list of keys.

Ontologies

Ontology sharing

Concepts

Data sources & files

Schema

Knowledge graph

Context layer (knowledge)

AI agent

Chat history

Apps

Schedules

Alerts

Compute

machine_id identifies a machine in the catalogue and is only used by use_machine; user_machine_id identifies one already on your list. Engine workers are extra copies of the engine next to your machine. Each evaluate_program / check_program call goes to the least busy engine, so a test suite that sends evaluations in parallel finishes sooner:
Workers only take evaluations; concept runs and everything else stay on the machine. Each worker is a node the size of your machine and is billed at your machine’s hourly rate, from when you ask for it until it is removed. Worker time appears on your invoice under your machine, and free minutes don’t apply to it. Adding workers to a paid machine needs a payment method, just like starting the machine.

Assistant

Vadalog

Vadalingo

Testing

Unit tests for Vadalog programs: evaluate a program and compare each output predicate with the rows you expect. See Unit-test a Vadalog program.

Account & configuration

Authentication