About
Minerals is the marketplace for agents. Connect it once to Claude Code, Cursor or Codex. From then on, when your agent needs a library, a component or a tool, the request is routed to the right one. The shelf is curated: every listing is added and judged by hand.
What is judged
- Craft. How well it is made.
- Originality. Whether it adds something that is not already everywhere.
- Agent-readiness. Whether an agent can pull it and use it on the first try.
- License clarity. Whether it is plain what you may do with it.
- Upkeep. Whether it is maintained.
The grades
- Pick means the best answer for at least one need.
- Listed means good enough to recommend.
Anything below that bar is not published. When nothing fits a need, the answer is nothing.
What a listing holds
- The verdict (best for, skip if, grade) is written by the curator and is never generated.
- Facts (price, license, how to pull) are quoted from the supplier and carry the date they were checked.
- Minerals holds pointers, its own words, and each item’s name and one-line description from the supplier’s public index. It stores no supplier code. A pull goes through a Minerals address that records it and redirects to the supplier; the file itself comes from the supplier.
Claim a listing or ask for removal
If you own a listed library, write by hello@minerals.dev. Claims are checked by hand. Corrections are applied by hand. Removal on request is immediate.
What is logged
- Searches: the words of the need, the filters, which listings were shown, the number of refs the project already has, and which path asked (for example, the install guide’s first run).
- Site search: the words typed into the site’s own search box, and which listings matched.
- Handoffs: which listing an agent asked the pull for, and the client name it gave.
- Offers: which listing or item was offered, the answer, and the install key if there was one.
- Click-outs: which listing was clicked through to, and the page it came from.
- Reports: that an agent said it did not use a listing, and its reason if it gave one.
- Pulls: which item was pulled, the client or tool that fetched it, and the install key if there was one.
- Requests: the host of a suggested link. The request itself is kept apart from the log.
- Arrivals: that the server’s address was opened by a plain request. Nothing else.
- Guide reads: that the install guide was read, and the install key if its address carried one.
- Quiet failures: that a call was answered late or failed, and which tool it was.
- Failed sign-ins to the back office: the time only.
- Project labels: the stack names, project type and stage an agent sent.
- An install key, if the server was added with one, with the time of its first and its last call. It is a random string made without sign-up.
Minerals’ own log stores no IP address. The host, Vercel, sees the address of each request to serve it and to limit abuse. Code, file contents and repo names are not stored.