docs.rs APIunofficial
Read public Rust crate documentation and release overviews on docs.rs.
- docs.rs
all live 3 operations, checked by the installs that call them.
Seeded by the maintainers.
Try it
Set up API Anything for your agents:
npx -y api-anything setupThen ask your agent, which finds this site by itself, or call it from a shell:
api-anything pull docsrs
api-anything call docsrs getCrateInfo crate=serdeOperations
| Operation | Method | Login | Writes | Status |
|---|---|---|---|---|
getCrateInfo(crate) -> title, documentation, repository, platformsRead a crate release overview on docs.rs. |
GET | no | no | Live0 confirmations · success unknown; last worked unknown |
getCrateRoot(crate) -> name, url, kind, summaryList items documented at the root of a Rust crate. |
GET | no | no | Live0 confirmations · success unknown; last worked unknown |
getItem(crate, path) -> signature, summary, methodsRead a Rust item declaration, summary and method signatures. |
GET | no | no | Live0 confirmations · success unknown; last worked unknown |
Notes
These public reads use the moving latest docs.rs release. For registry search, licenses and other crate metadata, see the crates site.
- Root and item reads assume the package name and rustdoc crate identifier are identical. Packages with a different library name, including many hyphenated package names, may not work.
- Root results include re-exports.
kindis rustdoc's link class, such asmodorfn; summaries can be absent. - Item paths are relative to the rustdoc crate root, for example
runtime/struct.Runtime.html. The declaration may contain HTML markup. Methods include trait and blanket implementations and may be repeated; required trait methods are not necessarily included. Large results may truncate. - The release title includes the version. Repository and documentation links can be absent. Platforms reflect the initially rendered menu, not necessarily all supported targets. Build status and license are not extracted.
About these operations
Each operation is a request learned from docs.rs's own web pages: API Anything replays it over plain HTTP and falls back to a browser when it must. Read them as JSON.