REST API
Releases, downloads, acceptance and webhooks are available under /api/v1. An OpenAPI document describes every route, so your engineers can read the schema before they write code.
Updates from skilled work & robotics.
Sign upCuratrix gives each customer organisation a REST API and a Python SDK. Your scripts list licensed releases, download and verify them, and confirm delivery. Access is by invitation.
Use the one that fits your stack. All three reach the same releases under the same access rules.
Releases, downloads, acceptance and webhooks are available under /api/v1. An OpenAPI document describes every route, so your engineers can read the schema before they write code.
A small Python library for the same tasks: pull, verify and accept releases, or upload footage for pre-labelling. We hand it to customers on request; it is not on PyPI.
Your system hears about a release the moment its status changes, without polling. Every message is signed, and a failed one is retried for about 18 hours.
Four tasks cover a delivery from start to finish: find a release, fetch it, sign it off and stay informed.
Page through the releases your organisation owns or licenses, and read one release with its manifest summary.
Request a short-lived download link for the archive or the LeRobot export. The checksum and the quality report do not count as a download.
Confirm ingestion and accept a release in one call, or reject it with a structured issue for the supplier to resolve.
Register an HTTPS endpoint and receive a signed event when a release is published, licensed to you or accepted, when a pre-labelling job is done and when a requested sample is ready.
Each customer organisation gets its own service keys. A key works only inside its organisation and only for what it was allowed to do.
An organisation admin creates a key in the application and names it after the integration. The key is shown once. We store only its hash.
A key carries the scopes chosen when it was made, such as read:releases and read:assets. Accepting deliveries and registering webhooks need their own write scopes.
A revoked key is rejected on its next request. A download link already issued expires after five minutes. Every call is logged against the key.
Access is by invitation. When a project starts, we set up your organisation in the application and your admin creates its keys. There is no self-service sign-up and no public base URL yet. Tell us about your integration in a technical call.