Embodied Schemas
Shared Pydantic schemas and factual hardware/model data for embodied AI hardware/software codesign.
Overview
This package provides:
- Pydantic Schema Models - Type-safe data structures for hardware platforms, ML models, sensors, use cases, and benchmarks
- Factual Data Catalog - YAML files with validated specifications for chips, dev kits, perception models, and sensors
- Registry API - Unified access to query and filter the data catalog
Installation
pip install embodied-schemas
# For development
pip install -e ".[dev]"
Usage
Import Schema Models
from embodied_schemas import (
HardwareEntry,
ModelEntry,
SensorEntry,
UseCaseEntry,
BenchmarkResult,
)
from embodied_schemas.hardware import HardwareType, PowerMode
from embodied_schemas.constraints import LatencyTier, PowerClass
Access Data Catalog
from embodied_schemas import Registry
# Load the catalog
registry = Registry.load()
# Look up hardware by ID
jetson_nano = registry.hardware.get("nvidia_jetson_nano_4gb")
# Find hardware matching criteria
edge_devices = registry.hardware.find(
suitable_for="edge",
power_watts_max=15
)
# Look up models
yolov8s = registry.models.get("yolov8s")
detection_models = registry.models.find(type="object_detection")
# Check compatibility
is_compatible = registry.is_compatible(
model_id="yolov8s",
hardware_id="nvidia_jetson_nano_4gb",
variant="fp16"
)
Use in Tool Outputs
from embodied_schemas import BenchmarkResult
from embodied_schemas.benchmarks import LatencyMetrics
result = BenchmarkResult(
model_id="yolov8s",
hardware_id="nvidia_jetson_nano_4gb",
variant="fp16",
verdict="PASS",
confidence="high",
latency=LatencyMetrics(
mean_ms=28.5,
std_ms=2.1,
p95_ms=32.0,
),
)
Data Catalog Structure
data/
├── hardware/ # Complete dev kits and platforms
│ ├── nvidia/
│ ├── qualcomm/
│ ├── hailo/
│ ├── google/
│ └── ...
├── chips/ # Raw SoC/chip specifications
│ ├── nvidia/
│ ├── qualcomm/
│ └── ...
├── models/ # ML model specifications
│ ├── detection/
│ ├── segmentation/
│ └── ...
├── sensors/ # Cameras, depth sensors, LiDAR
│ ├── cameras/
│ ├── depth/
│ └── lidar/
├── usecases/ # Application constraint templates
│ ├── drone/
│ ├── quadruped/
│ ├── amr/
│ └── edge/
└── constraints/ # Tier definitions
├── latency_tiers.yaml
└── power_classes.yaml
Related Projects
- graphs - Analysis tools, roofline models, simulators
- Embodied-AI-Architect - LLM orchestration, CLI, knowledge base
Contributing
Adding Hardware Data
- Create YAML file:
src/embodied_schemas/data/hardware/{vendor}/{name}.yaml - Follow the schema in
src/embodied_schemas/hardware.py - Run validation:
pytest tests/test_data_validity.py - Include datasheet URL in the file
Schema Changes
- Schema changes require version bump
- Breaking changes require major version bump
- Add deprecation warnings before removing fields
License
MIT License - see LICENSE file for details.
Metadata
Release files for embodied-schemas 0.9.0
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 | |
|---|---|---|---|---|
| embodied_schemas-0.9.0.tar.gz | 477.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embodied_schemas-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / embodied_schemas-0.9.0.tar.gz
| Download URL | embodied_schemas-0.9.0.tar.gz |
|---|---|
| Size | 477.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd1c1eba1616d67c527ab18ea64ed08bb64320725b3c60b87d109370c0e04fd3
|
|
BLAKE2b-256 checksum How to use checksums |
4a8f5b631ffb685a28418e0e65ccd3e745afde98fa69ab0dfbf513d848819518
|
| 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 Sep 15, 2026.
Transparency logRelease files / embodied_schemas-0.9.0-py3-none-any.whl
| Download URL | embodied_schemas-0.9.0-py3-none-any.whl |
|---|---|
| Size | 562.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24e1d22fd3c52dde5fe9d82970d9e37901e3ed2e5a45fff25259d2e7ae0e4cf9
|
|
BLAKE2b-256 checksum How to use checksums |
3367e52645fcf6301ce89095b5061f6c5b5a1b7e1d384563efebd3563a6edb0a
|
| 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 Sep 15, 2026.
Transparency logSecurity for embodied-schemas 0.9.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for embodied_schemas-0.9.0.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 Sep 15, 2026.
Transparency logA 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.