__Experimental API documentation for the [crates.io](https://crates.io/) package registry.__ This document describes the API used by the crates.io website, cargo client, and other third-party tools to interact with the crates.io registry. Before using this API, please read the [crates.io data access policy](https://crates.io/data-access) and ensure that your use of the API complies with the policy. __The API is under active development and may change at any time__, though we will try to avoid breaking changes where possible. Some parts of the API follow the "Registry Web API" spec documented at and can be considered stable. Most parts of the API do not require authentication. The endpoints that do require authentication are marked as such in the documentation, with some requiring cookie authentication (usable only by the web UI) and others requiring API token authentication (usable by cargo and other clients).
This provider-level handoff preserves only its public ID. No tool or business task is guessed; choose a current tool during rediscovery before setup can be treated as complete.
This information can also be obtained directly from the index. In addition to returning cached data from the index, this returns fields for `id`, `version_id`, and `downloads` (which appears to always be 0)
This returns a URL to the location where the crate is stored.
This includes the per-day downloads for the last 90 days.
This includes the per-day downloads for the last 90 days and for the latest 5 versions plus the sum of the rest.
List crate owners.
List user owners of a crate.
Get the readme of a crate version.
List reverse dependencies of a crate.
List all versions of a crate.
Get keyword metadata.
Find team by login.
Find user by login.
This currently only returns the total number of downloads for crates owned by the user.
