AGI Pages
agi-pages is the umbrella/provider package for AGILAB public analysis views.
It exposes a small discovery API so the AGILAB ANALYSIS page and exported
notebooks can resolve installed view bundles without embedding the page source
in the root agilab wheel.
The native UI described here is the current source implementation. Previously published PyPI packages may still use the former provider; the commands below install their published release, not this source migration. From an AGILAB source checkout, use
uv sync --extra ui --extra notebookto install the native interface and notebook widget. Local validation does not publish those changes.
Quick Install
pip install agi-pages
Most users should install it through the AGILAB UI profile:
pip install "agilab[ui]"
Runtime Contract
The package exposes a small provider API:
import agi_pages
print(agi_pages.bundles_root())
agi-env uses this provider only when agi-pages is installed. A base
agilab install remains CLI/core-only and does not require this package.
The default umbrella covers the shared AGILAB UI runtime. Specialized views
with narrower runtime constraints are published independently as agi-page-*
wheel/sdist payload packages. Install the page package you need alongside
agi-pages when a notebook or app depends on that view.
Portable Chart Specs
agi-pages also exposes a lightweight chart contract for page bundles that need
the same dataframe-driven visualization to work in native Python UI, exported
notebooks, and static proof artifacts.
import agi_pages
spec = agi_pages.build_chart_spec(
[{"step": "train", "accuracy": 0.84}, {"step": "test", "accuracy": 0.82}],
chart_type="line",
title="Model metrics",
x="step",
y="accuracy",
)
agi_pages.render_streamlit(spec) # compatibility name; renders with agi_web.python_ui
The spec stores an ECharts-compatible option, normalized table records, and a
small evidence block with deterministic hashes for the data, chart option, and
combined chart contract. Page bundles can write spec.as_dict() into a proof
artifact, render agi_pages.render_notebook(spec) from an exported notebook, or
embed agi_pages.chart_spec_to_static_html(spec) in a standalone HTML report.
Metadata
Release files for agi-pages 2026.10.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agi_pages-2026.10.10.1.tar.gz | 20.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agi_pages-2026.10.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.4 kB
Release files / agi_pages-2026.10.10.1.tar.gz
| Download URL | agi_pages-2026.10.10.1.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f68341d8e5372c1653b24ca9f92a01fb75ee24a332550d59f9becaf0288a68c
|
|
BLAKE2b-256 checksum How to use checksums |
ba375c842e4df37d2f9501dea950f917f1e31886dd4120df76db395e113a8559
|
| 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 Oct 11, 2026.
Transparency logRelease files / agi_pages-2026.10.10.1-py3-none-any.whl
| Download URL | agi_pages-2026.10.10.1-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86d877a6ab11036fe20f282fd09cf2c2f22d906efc807f3044ce5c9815f9c982
|
|
BLAKE2b-256 checksum How to use checksums |
d970b32eb8ade7674f34a08b4b9c026863e10e88a54a04ec1be2dde1e7be1fd6
|
| 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 Oct 11, 2026.
Transparency log