Skip to main content

041 Metrics API Client

Python client for the 041 Metrics v2 API. Use it to find and organize folders and experiments and to read one experiment's record, catalog, annotations, and series from code.

Pick the right tool:

  • Analysis across experiments: the o41-metrics-duckdb extension attaches Metrics as a database with an on-disk cache. Use it for plots, tables, joins, and anything spanning a folder.
  • Recording training or evaluation jobs: o41-metrics-collector queues, batches, and delivers metrics in the background. This client's write session exists for API completeness, tests, and backfills.
  • Programmatic control and one-experiment reads: this client.

Install

uv add o41-metrics-api

Connect

from o41_metrics_api import Metrics

metrics = Metrics()

The client resolves credentials the same way as the o41-metrics CLI. The API key comes from api_key=, then O41_METRICS_API_KEY, then the login saved by o41-metrics auth login. The host comes from host=, then O41_METRICS_HOST, then the saved login's host when the key came from that login, then https://metrics.041.io. Metrics is also a context manager that closes its HTTP session.

Folders and experiments

Address a folder by absolute path or id; / is the root. Address an experiment by id or slug.

mamba = metrics.make_folder("/models/mamba")  # creates missing parents
mamba = metrics.folder("/models/mamba")       # MetricsNotFound when missing
mamba.folders()                               # direct children
mamba.experiments()                           # direct members
mamba.experiments("run-*", recursive=True)    # slug glob, whole subtree
metrics.experiments("syv-2039-*")             # every experiment matching a glob

exp = metrics.experiment("mamba-run-001")
exp.move("/archive")
mamba.rename("mamba-v2")
mamba.move("/")

Lookups use a snapshot of the folder tree, read on first use. Changes made through the client refresh it. A folder() or experiment() lookup that misses reads the tree again once before raising. Listings such as folders() and experiments() use the snapshot as is, so call metrics.refresh() to list what was created elsewhere. Folder and Experiment are immutable values. A rename or move returns a new handle.

Read one experiment

info = exp.info()          # status, description, meta, error, lifecycle datetimes
catalog = exp.catalog()    # series names with their metadata keys and values
notes = exp.annotations()  # every annotation, newest first

for series in exp.series("loss", where={"split": "valid"}):
    print(series.metadata, series.steps, series.values)

series() returns one Series per metadata partition. Its steps, timestamps_ms, and values are aligned. Pass one name, several names, or none to read every series of the experiment. Results follow the order of the names, or name order when you pass none. One streaming request reads up to 1,000 series. where matches exact metadata values, has=("rank",) requires a key, and x="timestamp" orders points by time instead of step. The client returns series only after the stream completes, so partial data is never returned.

Write session

with metrics.open_experiment(
    "backfill-001", description="Imported run", meta={"seed": 7}, folder="/imports"
) as run:
    run.start()
    run.metric("loss", 0.25, step=1, metadata={"split": "train"})
    run.done()

Each call is one acknowledged request. metrics() takes many MetricPoints and sends up to 1000 per request. The session refreshes its experiment token before it expires and revokes the token when the block exits. Reopening an existing slug replaces its description and meta. An experiment already in another folder stays there. A token left idle past its 24 hour expiry cannot be refreshed, so reopen the experiment instead. For real training jobs use o41-metrics-collector.

Other events

metrics.send(event, data) sends any v2 organization event to /api/v2/events and returns the reply data. The API reference is at https://metrics.041.io/api/openapi.json.

Errors and retries

Every failure is a MetricsError with code, message, status, and retryable. MetricsNotFound (also a LookupError) reports an unresolved reference. MetricsAuthError reports missing credentials.

Reads and metric writes retry transient failures with backoff. A retried metric keeps its original message id, which the API deduplicates. Every other write never retries, because repeating it can have side effects: folder creation, moves, renames, open_experiment, lifecycle events (a replayed done would move done_at), annotations, and send().

Metadata

Release files for o41-metrics-api 0.1.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 o41-metrics-api 0.1.0
File Size Uploaded Provenance
o41_metrics_api-0.1.0.tar.gz 18.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for o41-metrics-api 0.1.0
File Interpreter ABI Platform
o41_metrics_api-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 39.9 kB

Release files / o41_metrics_api-0.1.0.tar.gz

Download URL o41_metrics_api-0.1.0.tar.gz
Size 18.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e0d2d5a794052c1fe13b719be1850beeb64ed7e02cb4801c535122a0eb294332
BLAKE2b-256 checksum
How to use checksums
2df8dba0bb4e785291ecd151cb7d7b13361df18efb81cd79d1cd331b2cf32fa0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / o41_metrics_api-0.1.0-py3-none-any.whl

Download URL o41_metrics_api-0.1.0-py3-none-any.whl
Size 21.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4b922655feb658cc2a70d955bb35a0b0e4f70067ca3bcbbd206a218572af4c31
BLAKE2b-256 checksum
How to use checksums
1cf13564c880f68d1a3ca01da2a8d673a0c2f9ea6203901434dcfb184bc90a5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for o41-metrics-api 0.1.0

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.

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