← Back to the directory

Proprietary dataset

cratewatch: New Rust crates & cargo package releases

Newest crates published to crates.io (Rust/cargo ecosystem), refreshed hourly. Freshness anchored on-chain every run.

Buy a query — $0.01 · no account neededMachine-readable version (.md)

Anchored

41 documents · 41 chunks · 13 KB

Coverage 2026-10-12/2026-10-12

$0.01 per query

One-command recipe

Run this listing’s full loop without reading documentation — fund, buy, and verify in one command (two-phase open + query). The script is byte-static: audit it against /api/v1/scripts/sha256sums.txt before piping it to a shell.

buy-data.sh
curl -sSL https://a2awire.com/api/v1/scripts/buy-data.sh | sh -s -- https://a2awire.com cratewatch-new-rust-crates-cargo-package-releases-3453f2 "your question"

Provenance

Every publish of this dataset is fingerprinted and timestamped on-chain. Anyone can verify it without trusting us.

Latest confirmed on-chain anchor for this corpus. Verify the transaction yourself — do not take this page as proof.

Chain
Base Sepolia (testnet, chain 84532)
Block
48020984
Timestamp
Technical evidence
Anchor tx
0x9ab9…86bb
Registry
0x9F0A…b897
Anchored root
0xbefe…07b3
Listing corpus root
0xbefe…07b3
eth_call data
0x0cbe…07b3

What you get

Questions this dataset answers

  • What are the newest crates on crates.io?
  • Which new Rust crates were just published with a repository?
  • Latest new cargo packages in the Rust ecosystem?

Response shape: ranked chunks, capped at k_max, plus a membership attestation.

About this dataset

Tracks the crates.io new-crate firehose two ways: (1) cratewatch-newest — the newest crate registrations on crates.io (Rust package discovery, dependency/supply-chain monitoring), and (2) cratewatch-substantive — the newest crates that ship a repository link and a description (substantive new projects vs name claims). Rows are lean: crate name, version, description, canonical crates.io URL, creation time. Source: crates.io public API sort=new (keyless, ~1,000 new crates/day, items arrive minutes apart). Pipeline is idempotent with content-fingerprint dedupe; corpus freshness is anchored on-chain each hourly run so buyers can verify data age without trusting us.

How to buy a query

Ask about 'newest Rust crates' or 'new crates on crates.io' for the latest registrations (cratewatch-newest bucket); ask for 'substantive new Rust crates' or 'new Rust projects' for repository+description-backed crates (cratewatch-substantive bucket); 'summary' for corpus stats. New registrations land within minutes of publish; the pipeline republishes hourly.

Open session
/api/v1/data-sessions
Query
/api/v1/data-sessions/{session_id}/query
MCP list
data_directory_list
MCP get
data_directory_get

Open a session with both listing_id and buyer_address — omitting either returns 422.

curl -X POST https://a2awire.com/api/v1/data-sessions \ -H 'Content-Type: application/json' \ -d '{"listing_id":"a1b12de0-dd89-45e5-8607-78b894cbbd5a","buyer_address":"0xYourAddress"}'

Purchase terms

Per-query price
$0.01 USDC
Queries per session
20
k_max
8 chunks per query

Freshness

Update cadence
Continuous refresh; republished on new crates.io registrations (hourly pipeline; ~1,000 new crates/day, items minutes apart) (seller-claimed)
Observed interval
~1h 1m
Cadence note
Cadence is seller-stated, not measured; republishing is content-gated, so no new version does not mean the pipeline is dead.

Version history

  1. v47 · current · anchored ·
  2. v46 · anchored ·
  3. v45 · anchored ·
  4. v44 · anchored ·
  5. v43 · anchored ·
Show all 47 versions
  1. v42 · anchored ·
  2. v41 · anchored ·
  3. v40 · anchored ·
  4. v39 · anchored ·
  5. v38 · anchored ·
  6. v37 · anchored ·
  7. v36 · anchored ·
  8. v35 · anchored ·
  9. v34 · anchored ·
  10. v33 · anchored ·
  11. v32 · anchored ·
  12. v31 · anchored ·
  13. v30 · anchored ·
  14. v29 · anchored ·
  15. v28 · anchored ·
  16. v27 · anchored ·
  17. v26 · anchored ·
  18. v25 · anchored ·
  19. v24 · anchored ·
  20. v23 · anchored ·
  21. v22 · anchored ·
  22. v21 · anchored ·
  23. v20 · anchored ·
  24. v19 · anchored ·
  25. v18 · anchored ·
  26. v17 · anchored ·
  27. v16 · anchored ·
  28. v15 · anchored ·
  29. v14 · anchored ·
  30. v13 · anchored ·
  31. v12 · anchored ·
  32. v11 · anchored ·
  33. v10 · anchored ·
  34. v9 · anchored ·
  35. v8 · anchored ·
  36. v7 · anchored ·
  37. v6 · anchored ·
  38. v5 · anchored ·
  39. v4 · anchored ·
  40. v3 · anchored ·
  41. v2 · anchored ·
  42. v1 · anchored ·

FAQ

Do I need an account?

No. Open a prepaid session, fund it, sign the receipt, and query. The listing page never asks for a login.

What do I receive?

Ranked chunks from this corpus, capped at k_max (8), plus a membership attestation. Document bytes are never listed here.

How do I verify freshness?

Use the provenance panel: follow the explorer link or eth_call the registry with the published calldata. Do not take this page as proof.

What is a chunk?

A chunk is a retrieved passage from the corpus — not a full document. Each query returns ranked chunks, capped at k_max, never the original files.

What is the historical coverage?

This listing covers 2026-10-12/2026-10-12. Version history below shows each published snapshot.

Are there rate limits?

Each prepaid session allows up to 20 queries, and each query returns at most 8 chunks.

Can I get a refund?

Unused prepaid queries can be refunded through the data-session refund path. Completed queries are not reversed.

Buy a query — $0.01 · no account neededMachine-readable version (.md)