Skip to main content

basyx-registry-client

Python client library for AAS Registry APIs (IDTA-01002 Part 2, v3.x).

This library enables service discovery via AAS Registry APIs, allowing you to resolve Asset Administration Shell identifiers to their endpoint URLs. It complements the basyx-client repository client by providing the registry lookup layer in the workflow: ID → Registry → Endpoint → AASClient → Data.

Installation

pip install basyx-registry-client

With optional basyx-client integration:

pip install basyx-registry-client[basyx]

For development:

pip install basyx-registry-client[dev]

Quickstart

from basyx_registry_client import AsyncRegistryClient, RegistryClient

# Create a registry client
client = RegistryClient(base_url="https://registry.example.com/api/v3.0")

# List all shell descriptors
for descriptor in client.iter_shell_descriptors():
    print(f"AAS: {descriptor.id}")

# Resolve an AAS endpoint by its identifier
aas_id = "https://example.com/aas/motor-001"
endpoint = client.resolve_aas_href(aas_id)
print(f"Endpoint URL: {endpoint}")

# Optional filters
page = client.list_shell_descriptors(id_short="Motor001", asset_kind="Instance")
print(f"Filtered page size: {len(page)}")

# Async usage
async with AsyncRegistryClient(base_url="https://registry.example.com/api/v3.0") as client:
    descriptor = await client.get_shell_descriptor(aas_id)
    print(f"Found: {descriptor.id_short}")

With basyx-client integration:

from basyx_registry_client import RegistryClient
from basyx_registry_client.integrations import aas_client_from_registry

registry = RegistryClient("https://registry.example.com/api/v3.0")
aas = aas_client_from_registry(registry, "urn:example:aas:1")
shell = aas.get_shell("urn:example:aas:1")

Features

  • Synchronous and asynchronous API support
  • Full type annotations with Pydantic models
  • Compliant with IDTA-01002 Part 2, v3.x specification
  • Shell and submodel descriptor CRUD operations
  • Optional idShort/assetKind filters for shell descriptor listings
  • Resolve identifiers to preferred endpoints

API Reference

Documentation coming soon.

License

Apache-2.0

Metadata

Release files for basyx-registry-client 0.1.1

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

Source distribution (sdist)

Source distribution for basyx-registry-client 0.1.1
File Size Uploaded Provenance
basyx_registry_client-0.1.1.tar.gz 17.3 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for basyx-registry-client 0.1.1
File Interpreter ABI Platform
basyx_registry_client-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 43.2 kB

Release files / basyx_registry_client-0.1.1.tar.gz

Download URL basyx_registry_client-0.1.1.tar.gz
Size 17.3 kB
Tags Source
SHA-256 checksum
How to use checksums
fd9800a044c9e4b0a3b9c9ca8034f689dd653aedf657fde4c701094e035df292
BLAKE2b-256 checksum
How to use checksums
397b2d68bea3d1afb9a8615deb9d051ed8ee2dea06ae8b805485c1230a18117b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 22, 2026.

Transparency log

Release files / basyx_registry_client-0.1.1-py3-none-any.whl

Download URL basyx_registry_client-0.1.1-py3-none-any.whl
Size 25.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
22955cfe73f2bb669d2086740723c3ef228ba339b75f03a956d8987ad3c1c2d1
BLAKE2b-256 checksum
How to use checksums
c56ee09ee5cb87723588876bfcc593cbb9aca8f3ad505bb7f915e4d105a362e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 22, 2026.

Transparency log

Security for basyx-registry-client 0.1.1

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for basyx_registry_client-0.1.1.tar.gz

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 Jan 22, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

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