Ingest sensor data
Bring MCAP, LiDAR, video, ROS bags, or LeRobot data into one dataset model.
Physical AI developer platform
Connect your agents to the hosted MCP server, build on the Python and TypeScript SDKs, read the metadata on every sequence, and import or export LeRobot datasets.
Hosted MCP
Connect one hosted endpoint. Your agents can read fleet recordings and alerts, sequences, capture campaigns and their acceptance coverage, consensus, quality targets and export status.
Collection briefs, gap reports and evaluation reports come with the fleet learning program. Your Avala team delivers them.
Read the MCP guidehttps://mcp.avala.ai/mcpTools by loop stage
fleet_list_recordingsfleet_list_eventsfleet_list_alertslist_sequencespreview_curation_candidateslist_capture_campaignsget_campaign_acceptance_coverageget_dataset_healthget_consensus_summarylist_quality_targetslist_sliceslist_exportsget_export_statusAccess follows your Avala permissions. Reviewed staff actions appear only for eligible operators and require explicit confirmation.
Interfaces
Python, TypeScript, the public REST API, and hosted MCP share the same Avala data model.
Sync and async clients, cursor pagination, typed models, and explicit errors.
pip install avalaTyped resource clients with zero runtime dependencies and formal support for Node.js 18+.
npm install @avala-ai/sdkUse the public api.avala.ai endpoint from any language or authenticated HTTP client.
curl --fail-with-body -H "X-Avala-Api-Key: $AVALA_API_KEY" "https://api.avala.ai/api/v1/datasets/?limit=10"Connect compatible AI tools to permission-scoped dataset and operations context.
https://mcp.avala.ai/mcpSequence metadata
Sequences delivered through a fleet learning program carry the same fields. Your training code can filter, split and weight them without guesswork.
See how each sequence is gradedLeakage groups let you split training and test sets so that the same home, object or operator never appears on both sides.
LeRobot
Import a LeRobot dataset into Avala as MCAP sequences, or export an Avala sequence dataset as a LeRobot v3 dataset. Each LeRobot episode maps to one Avala sequence. Both commands ship with the Python SDK and need Python 3.12 or later.
pip install "avala[cli,lerobot]"avala import lerobot --repo-id lerobot/svla_so101_pickplace --name "SO-101 pick and place" --slug so101-pick-and-placeavala lerobot export my-org/so101-pick-and-place --repo-id my-hf-user/so101-pick-and-place --output ./lerobot-outFirst loop
Enter your key through a no-echo prompt and query the public API while the credential stays isolated inside a temporary shell.
Bash or Zsh · curl · an Avala API key
(
printf "Avala API key: " &&
IFS= read -rs AVALA_API_KEY &&
printf "\n" &&
export AVALA_API_KEY &&
curl \
--fail \
--silent \
--show-error \
-H "X-Avala-Api-Key: $AVALA_API_KEY" \
"https://api.avala.ai/api/v1/datasets/?limit=10"
)Programmable workflow
Use stable interfaces for the operational steps between raw sensor data and the next model run.
Bring MCAP, LiDAR, video, ROS bags, or LeRobot data into one dataset model.
Check indexing, sequences, frame counts, and calibration before data enters production.
Launch project-scoped auto-label jobs and keep human review inside the same governed workflow.
Create a dataset or project export and track it through completion for downstream training.
Technical walkthrough
We will map the interfaces, storage path, quality gates, and release contract around one real workflow.