crates.io
crates.io · Developer tools
Rust package registry: crates, versions, owners and tokens
The client pastes their API token from crates.io's settings. We store it encrypted.
Tested against crates.io's live API.
Building with crates.io? The docs have setup steps and code for every tool.
Open the crates.io docsTools
Your agent calls any endpoint of crates.io's API with the request tool, with the client's access attached.
Base URL for request
https://crates.io/api/v1
request
HTTPS ANY /v1/clients/{clientId}/crates-io/{path}
Any endpoint of crates.io's own API, with the client's access attached.
- servicestringrequired
- This service: crates-io
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://crates.io/api/v1
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the crates.io key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.