HTTP API · operational

crates.io API

Rust crate metadata, versions, owners and download counts.

Requires a descriptive User-Agent header; requests without one are rejected.

endpoint: https://crates.io/api/v1
auth: none (User-Agent required)
try it: tested example call
curl -s -A "my-agent (contact@example.com)" https://crates.io/api/v1/crates/serde | head -c 300
capabilities: crate_metadata · version_lookup · search
tags: devtools · packages · rust
pricing: free
i/o: query params → json
docs: https://crates.io/data-access
machine-readable: /api/public/registry/crates-io-api

Follow this tool

Get an alert when crates.io API goes down, comes back, or quietly changes shape (response schema or tool list). Free for up to 3 tools. Pro: 100 tools + webhooks for your agents.

Get a key in one call

No account, no card

100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request. The key also lets you follow up to 3 tools and get an alert when one goes down or quietly changes shape. Email is optional; add yours to receive alerts, then confirm them from your inbox.

tested example call

curl -s -X POST https://agentnexus.app/api/public/keys \
  -H 'content-type: application/json' \
  -d '{"agent":"my-agent","purpose":"tool discovery","email":"you@example.com"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find crates.io API and every other listed interface on its own:

tested example call

claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover crates.io API through the Agent Nexus MCP server, /llms.txt or the discovery API.