RAGent Core
Shared data-source loaders, Turbopuffer retrieval, agent search tools, judges, types, utilities, and operational scripts.
Setup
Install locked runtime dependencies and configure the required API key:
uv sync --locked
cp .env-template .env
TURBOPUFFER_API_KEY is the only required retrieval setting. The defaults are
region gcp-us-central1, physical namespace prefix ragent, and logical
namespace default. Region and prefix can be overridden before building with
TURBOPUFFER_REGION and TURBOPUFFER_NAMESPACE_PREFIX.
Each corpus has a chunk namespace, a document namespace, and a catalog entry. The catalog records physical resolution, schema version, exact counts, vector availability and dimensions, embedding model, and readiness. Runtime reads reject missing or incomplete entries. Builders never overwrite a corpus; use a new logical namespace for a rebuild.
Build corpora
Run scripts from the repository root. Build all Hugging Face sources:
uv run --project ragent_core python ragent_core/scripts/build_turbopuffer_indexes.py \
--device cuda --batch-size 512
Build one source or a lexical-only corpus:
uv run --project ragent_core python ragent_core/scripts/build_turbopuffer_indexes.py \
--data-source nampdn_ai_devdocs_io --device cuda --batch-size 512
uv run --project ragent_core python ragent_core/scripts/build_turbopuffer_indexes.py \
--data-source nampdn_ai_devdocs_io --no-embedding --namespace lexical-v1
Build PersonaHub, optionally with --limit 100 for a smoke test:
uv run --project ragent_core \
python ragent_core/scripts/build_personahub_turbopuffer_index.py \
--device cuda --batch-size 512
Embeddings and writes are streamed in batches. Corpus document and chunk IDs are stored directly as Turbopuffer unsigned integers.
Delete namespaces
Pass explicit physical namespace names. The command only previews its targets
unless --yes is supplied:
uv run --project ragent_core \
python ragent_core/scripts/delete_turbopuffer_namespaces.py \
ragent.test.example.chunks \
ragent.test.example.documents \
ragent.test.catalog
uv run --project ragent_core \
python ragent_core/scripts/delete_turbopuffer_namespaces.py --yes \
ragent.test.example.chunks \
ragent.test.example.documents \
ragent.test.catalog
Data-source publication
Validate or upload normalized Hugging Face source data with:
uv run --project ragent_core python ragent_core/scripts/upload_data_source.py \
posthog_com --dry-run
uv run --project ragent_core python ragent_core/scripts/upload_data_source.py posthog_com
Generated-data publication belongs to the
data_pipelines project.
Metadata
Release files for ragent-core 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ragent_core-0.4.2.tar.gz | 378.9 kB | Without provenance | Details for ragent_core-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ragent_core-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for ragent_core-0.4.2-py3-none-any.whl |
Total release size: 427.9 kB
Release files / ragent_core-0.4.2.tar.gz
| Download URL | ragent_core-0.4.2.tar.gz |
|---|---|
| Size | 378.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64b8eb2ce3ff267c31ca8f20a55221421e192a416fbece97862cc0789ffe2e7b
|
|
BLAKE2b-256 checksum How to use checksums |
3c7c91f67ddeb544434a83b67ca2f82eadbcd026c412c15a61f272b2b5a1fa65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ragent_core-0.4.2-py3-none-any.whl
| Download URL | ragent_core-0.4.2-py3-none-any.whl |
|---|---|
| Size | 49.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
732a6382e1b09e98ac25f7284a5a784df72c9ca669918bc0430c60c461199ecd
|
|
BLAKE2b-256 checksum How to use checksums |
5049c18ef20cd52ec391a2caf1f4ce7cce89f4ffa6443c23fcc82b46fdd4d86d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ragent-core 0.4.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.