NucliaDB Agentic API

The NucliaDB Agentic API package exposes NucliaDB-oriented agentic capabilities for Hyperforge, including ASK/search flows and MCP integrations.

Install

From the workspace root:

uv sync

Run

Start the service:

uv run nucliadb-agentic-api

Useful endpoints:

/health/ready
/health/alive
/metrics

Configuration

Runtime configuration is provided through environment variables consumed by Pydantic settings. Common settings include:

HTTP_HOST and HTTP_PORT
MEMORY_READER_NUCLIADB, MEMORY_WRITER_NUCLIADB, and MEMORY_SEARCH_NUCLIADB
MEMORY_APIKEY_NUCLIADB
VALKEY_URL
IDP_REGIONAL_GRPC
LOAD_MODULES

Development

Run the package tests from the workspace root:

make test

Objective

Enhance the RAG experience by offering RAO features directly in a KB.

How?

The same way we store search configs in the KB, we could store agentic configs, and when calling the /ask endpoint we can refer to a given agentic config.

Scope

The corresponding RAO workflow will be:

a Rephrase (optionally)
a SmartAgent
a Summarize

Possible sources for the SmartAgent:

The current KB (possibly several times with different filters)
Sync service (using connections defined in the current KB)
Google
Perplexity
MCP

Out of scope

Other KBs
SQL
Snowflake (?)
Sitefinity (?)

Config spec

{
  "rephrase": { // optional
    "ask_to": <filter_expression>, //optional
    "prompt": <string>, // optional
    "model": <model>, // optional
  },
  "smart_agent": {
    "mode": <reactive | plan_execute>,
    "extra_prompt": <string>, // optional
    "models": { // optional
      "context_validation": <model>, // optional
      "planner": <model>, // optional
      "executor": <model>, // optional
    },
    "sources": [<source list>]
  },
  "summarize": { // optional
    "user_prompt": <string>, // optional
    "system_prompt": <string>, // optional
    "conversational": <boolean>,
    "model": <model>, // optional
    // and citations must be forced to chunk-level
  }
}

And sources can be:

{
  "type": "nucliadb",
  "description": <string>,
  "filter_expression": <filter_expression>, //optional
}

{
  "type": "sync",
  "description": <string>,
  "connection": <connection_id>
}

{
  "type": "google",
  "description": <string>
}

{
  "type": "perplexity",
  "description": <string>
}

{
  "type": "mcp",
  "description": <string>,
  <...the MCP driver params>
}

Metadata

Release files for nucliadb-agentic-api 1.0.0.post172

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

Source distribution (sdist)

Source distribution for nucliadb-agentic-api 1.0.0.post172
File	Size	Uploaded
nucliadb_agentic_api-1.0.0.post172.tar.gz	39.9 kB	Jul 23, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for nucliadb-agentic-api 1.0.0.post172
File	Interpreter	ABI	Platform	Reset
nucliadb_agentic_api-1.0.0.post172-py3-none-any.whl 48.7 kB Jul 23, 2026	Python 3	none	any	Details

Total release size: 88.6 kB

Release files / nucliadb_agentic_api-1.0.0.post172.tar.gz

Download URL	nucliadb_agentic_api-1.0.0.post172.tar.gz
Size	39.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`38ba475512857fdc6b1a479383f46360fdd7823a1d140ab06403dabb5656ddd6`
BLAKE2b-256 checksum How to use checksums	`405c3e3f47cce320ddfa9ea1e40e38bfd14a40ff6ba13a266a236281d16507c5`
Upload date	Jul 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.13`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nuclia/nucliadb_agentic_api
Publishing commit: github.com/nuclia/nucliadb_agentic_api/tree/ae6a8cf56d89e098c742ebe7310b4482220b3344

Workflow

Publishing configuration: github.com/nuclia/nucliadb_agentic_api/blob/ae6a8cf56d89e098c742ebe7310b4482220b3344/.github/workflows/nucliadb_agentic_api_workflow.yaml
Publishing logs: github.com/nuclia/nucliadb_agentic_api/actions/runs/29995729623/attempts/1

Artifact

Subject: nucliadb_agentic_api-1.0.0.post172.tar.gz
SHA-256 checksum: 38ba475512857fdc6b1a479383f46360fdd7823a1d140ab06403dabb5656ddd6 Verifying attestations

Release files / nucliadb_agentic_api-1.0.0.post172-py3-none-any.whl

Download URL	nucliadb_agentic_api-1.0.0.post172-py3-none-any.whl
Size	48.7 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`6bd488484acaa765e4553dd721f0bcb4bfcd8f9ae44080638b64ccef4c63399c`
BLAKE2b-256 checksum How to use checksums	`fdeeb9f5f9a96dfab78e13409845b481ad9c667373a8cf8502ef84bec03a8957`
Upload date	Jul 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.13`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nuclia/nucliadb_agentic_api
Publishing commit: github.com/nuclia/nucliadb_agentic_api/tree/ae6a8cf56d89e098c742ebe7310b4482220b3344

Workflow

Publishing configuration: github.com/nuclia/nucliadb_agentic_api/blob/ae6a8cf56d89e098c742ebe7310b4482220b3344/.github/workflows/nucliadb_agentic_api_workflow.yaml
Publishing logs: github.com/nuclia/nucliadb_agentic_api/actions/runs/29995729623/attempts/1

Artifact

Subject: nucliadb_agentic_api-1.0.0.post172-py3-none-any.whl
SHA-256 checksum: 6bd488484acaa765e4553dd721f0bcb4bfcd8f9ae44080638b64ccef4c63399c Verifying attestations