Skip to main content

liyaengine

Official Python client for the Liya Engine public API.

Status: early access. This SDK currently covers Domains, Intents, Collections, Agents, Workflows, and Evaluations. More resources (Run, Guardrail Policies) ship incrementally — see Roadmap.

Install

pip install liyaengine

Quickstart

from liyaengine import LiyaEngine

client = LiyaEngine(api_key="liya_...")

collection = client.collections.create(
    slug="contracts",
    label="Contracts",
    domain_keys=["legal-ops"],
)

collections = client.collections.list()

Or as a context manager (closes the underlying HTTP connection pool automatically):

with LiyaEngine(api_key="liya_...") as client:
    collections = client.collections.list()

Get an API key from your Liya Engine dashboard under Settings → API Keys.

Domains & Intents

A Domain is the top-level container most tenants configure first; Intents live under it.

domain = client.domains.create(domain_key="billing", display_name="Billing")

intent = client.domains.intents.create(
    "billing", intent_key="refund-status", display_name="Refund Status",
    prompt_template="You are a billing assistant. Question: {{message}}",
)

# Direct retrieval — no LLM call, useful for testing knowledge scoping.
result = client.domains.query("billing", query="refund timeline")

Basic CRUD only today — richer config (agent mode, retrieval tuning, guardrail policy attachment, prompt versioning) is still dashboard-only. domains.update()/domains.intents.update() return {"updated": 1}, not the updated object — call get()/list() again for the fresh state. There's also no get-one-intent route; use intents.list(domain_key).

Collections

client.collections.list()
client.collections.get(id)
client.collections.create(slug=..., label=..., domain_keys=[...])
client.collections.update(id, label=..., tags=[...], visibility=...)
client.collections.delete(id)

Full field reference: Collections API. Document ingestion beyond a quick file drop (domains.upload_document()) is still dashboard-only.

Agents

agent = client.agents.create(
    agent_key="support-triage",
    name="Support Triage",
    goal="Triage incoming support tickets and route them to the right team.",
)

# Agents are created in draft status — deploy to activate for execution.
client.agents.deploy(agent.agent_key)

result = client.agents.run(agent.agent_key, input={"message": "My order hasn't arrived yet."})

history = client.agents.list_runs(agent.agent_key)

Workflows

workflow = client.workflows.create(
    name="Lead Intake",
    steps=[{"step_type": "trigger", "config": {"trigger_subtype": "webhook"}}],
)

# Workflows are created in draft status — deploy to publish and make them
# callable. Deploying a webhook-triggered workflow for the first time mints
# its webhook secret; capture it immediately, it is never returned again.
deployed = client.workflows.deploy(workflow.workflow_key)
webhook_url, webhook_secret = deployed["webhook_url"], deployed["webhook_secret"]

# Roll the secret with a grace window so in-flight senders don't break.
client.workflows.rotate_webhook_secret(workflow.workflow_key, grace_period_seconds=300)

# Flip a deployed workflow on/off without touching its definition.
client.workflows.toggle(workflow.workflow_key)

result = client.workflows.run(workflow.workflow_key, input={"email": "ada@example.com"})

history = client.workflows.list_runs(workflow.workflow_key)

deploy() and rotate_webhook_secret() return the plaintext webhook secret exactly once. Store it immediately — subsequent reads (get, list) only ever expose trigger_config["has_secret"].

Evaluations

A Suite binds a Dataset to one specific intent; suites.run() calls that intent for real and scores what it produces. runs.submit()/evaluations.score() score a response you already generated yourself — no intent execution involved.

dataset = client.evaluations.datasets.create(
    name="Support Replies",
    cases=[{"input": {"message": "Where is my order?"}}],
)

suite = client.evaluations.suites.create(
    name="Order Status Suite",
    domain_key="support",
    intent_key="order-status",
    dataset_id=dataset.id,
)

# Runs are always async — poll for status/results.
run = client.evaluations.suites.run(suite.id)
result = client.evaluations.runs.get(run.id)

# A failed run can be resumed — already-scored cases are skipped.
client.evaluations.runs.resume(run.id)

# Score a response you already generated, no dataset/suite required.
scored = client.evaluations.score(
    input={"message": "Where is my order?"},
    output="Your order shipped yesterday and should arrive by Friday.",
)

custom_scorer_webhook_secret on a Suite is write-only — it's never returned; only a custom_scorer_webhook_secret_set boolean comes back on reads.

Error handling

Every failed request raises LiyaEngineAPIError, carrying the API's code, message, and HTTP status:

from liyaengine import LiyaEngineAPIError

try:
    client.collections.create(slug="contracts", label="Contracts", domain_keys=["legal-ops"])
except LiyaEngineAPIError as err:
    if err.code == "SLUG_CONFLICT":
        # handle the conflict
        pass
    raise

Network failures and timeouts raise LiyaEngineNetworkError instead. Requests are retried automatically on 429/5xx responses and transient network errors (2 retries by default).

Configuration

LiyaEngine(
    api_key="liya_...",
    base_url="https://api.liyaengine.ai",  # override for local/staging
    timeout_s=30.0,
    max_retries=2,
)

Roadmap

  • Domains & Intents (basic CRUD, direct retrieval query, narrow document upload — richer config still dashboard-only)
  • Collections
  • Agents (full CRUD, deploy, run, run/session history)
  • Workflows (full CRUD, toggle, deploy, webhook secret rotate, run, run history)
  • Evaluations (Datasets/Cases/Suites/Runs/Reviews CRUD, suite execution, cancel/resume, statistical + pairwise compare, standalone scoring)
  • Full KBaaS (document list/get/delete, async ingestion jobs + URL crawl, collection↔document/domain attach-detach, analytics)
  • Domain/Intent config parity (agent/execution/retrieval/cache config, guardrail policy attachment, versioning)
  • Run / Run (streaming)
  • Guardrail Policies
  • Prompt Studio (holding until the feature itself is committed/merged upstream)
  • Async client

Full docs: https://liyaengine.ai/docs/sdks/python

Development

python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
mypy src
pytest

License

MIT

Release files for liyaengine 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for liyaengine 0.5.0
File Size Uploaded
liyaengine-0.5.0.tar.gz 23.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for liyaengine 0.5.0
File Interpreter ABI Platform
liyaengine-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 44.6 kB

Release files / liyaengine-0.5.0.tar.gz

Download URL liyaengine-0.5.0.tar.gz
Size 23.4 kB
Tags Source
SHA-256 checksum
How to use checksums
e9571c526b8f6d4ea32027ff4bb1af08f4ba99ff25fbac3fe23d2dbe99fb25c1
BLAKE2b-256 checksum
How to use checksums
2fee27608a91b80435b4830644063e4047a0bae6e924071ccde26c73793db0c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release files / liyaengine-0.5.0-py3-none-any.whl

Download URL liyaengine-0.5.0-py3-none-any.whl
Size 21.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
60a26896b457d1a04a698879542bd3bf642f8bc67d5ef77114024a5e9574664d
BLAKE2b-256 checksum
How to use checksums
18fae203fb90a1e60871692354516281f42165efe29083d741ef71e45fa6da03
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.0

2 release files

0.7.0

2 release files

0.6.0

2 release files

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page