Roadmap
Now, next, later.
AgentsUse builds in the open from its own market map. This page separates what is live from what is in early access and what is only direction. It carries no dates, quarters, or ship promises: an item moves when the evidence and the product are ready, and the changelog records it when it lands.
Now
Live today
Public market map
Tool, MCP server, and framework profiles, category archives, curated stacks, and gated comparison and integration pages, each checked against primary sources.
Harness patterns
Nine sourced patterns, three long-form guides, harness notes in selected profiles, and the framework comparison on production tool behavior.
Browser workspace
Saved stacks with JSON and CSV export, plus a watchlist, stored in your browser. Catalog API access is open by request.
Next
Early access and active direction
Claude enrichment in the review pipeline
The enrichment module is built into ingestion and produces drafts for human review only. It stays feature-flagged off until API credits are in place.
Catalog API early access
Structured access to verified catalog records, compatibility records, and check dates for builders who need the map as data.
Change alerts
Notifications for watched entries when a new version ships, pricing changes, or a listing goes stale. Alerts are part of the Pro direction and are not sent yet.
Later
Direction, with no date attached
Account-synced stacks
Stacks and watchlists that follow an account across devices, with sharing, once real accounts replace the browser-local workspace.
The AgentsUse framework
A harness layer built from the published patterns and the gaps the catalog keeps exposing: compatibility from verified records, permission and audit controls, and reference patterns as code. Upcoming, not shipped, and not dated.
Owned tools from catalog gaps
APIs, MCP servers, and SDKs built where the market map shows a repeated gap. Each one ships only when the evidence supports a product, under the same verification rules as the catalog.
How items move
The catalog is the filter. Candidate records become drafts, drafts become verified profiles, and the gaps that survive that process shape what gets built next. AI assistance follows the same rule: Claude enrichment drafts into the human review queue and never publishes on its own, as described on the security page.
The operating model behind this roadmap is the same harness discipline. Agents research, classify, and draft inside the ingestion pipeline; schema checks validate the drafts; human review gates every publish. Agents working as operators under those controls are how a small company keeps the map current while still building toward owned tools, and the product line sells that same discipline to other builders.
Developers can read the Catalog API early access notes, compare Free and Pro on the pricing page, and request access through the contact page.