Marketplace
Browse agents by ARP.
rensei marketplace lets you discover agent configurations published to the Rensei Agent Registry. Browse by work type or provider - there is no CLI command that dispatches a session directly from a card ID (see Dispatching an agent from the marketplace below).
Command
marketplace browse
Browse available agents in the Agent Registry.
rensei marketplace browse \
[--work-type <type>] \
[--provider <id>] \
[--json]| Flag | Description |
|---|---|
--work-type <type> | Filter by work type (e.g. development, research, qa, code-review, planning) |
--provider <id> | Filter by Agent Registry Provider (ARP) ID (e.g. local, arp-github-marketplace) |
--json | Emit results as a JSON array |
# Browse all available agents
rensei marketplace browse
# Find agents for code review work
rensei marketplace browse --work-type code-review
# Browse agents published by a specific provider
rensei marketplace browse --provider arp-github-marketplace
# Machine-readable output
rensei marketplace browse --work-type development --jsonExample output:
CARD ID NAME WORK TYPE PROVIDER VERSION
card_abc123 TypeScript Backend development local 1.0.0
card_def456 Security Reviewer code-review arp-github-mktpl 2.1.0
card_ghi789 QA Automation Agent qa local 0.9.1
card_jkl012 Research Synthesizer research arp-acme-internal 1.2.3Example JSON output:
[
{
"id": "card_abc123",
"name": "TypeScript Backend",
"description": "Full-stack TypeScript development agent with Node.js toolchain",
"workType": "development",
"providerId": "local",
"version": "1.0.0",
"capabilities": ["typescript", "nodejs", "postgres", "testing"],
"authModes": ["host-session", "local", "metered"],
"updatedAt": "2026-05-20T10:00:00Z"
}
]Dispatching an agent from the marketplace
There is no rensei agent run-card command (an earlier version was removed
2026-07-27 - it printed a false "dispatched" confirmation without ever
POSTing a dispatch request). There is currently no CLI flag that dispatches a
session from a card ID directly.
dispatch does not take a card ID directly. The platform resolves cards by a
most-specific-wins cascade (workflow → project → org → system) filtered by
workType. To make a marketplace card win the resolution for a project, an
org-admin promotes it into that org/project's scope (project UI: Factory →
Agent Cards → New card, or POST /api/agent-cards) with the matching
workTypes, then dispatch normally:
rensei dispatch --project my-fintech-app --goal "<free-text goal>" --work-type <research|implement|review> --waitSee Agent cards CLI and Agent cards overview for the full card resolution model.
Agent Registry Providers (ARP)
The marketplace is backed by one or more Agent Registry Providers. Each ARP is an implementation of the IAgentRegistryProvider interface and can serve a different catalog:
| Provider ID | Source | Description |
|---|---|---|
local | Your org | Agent cards authored and published within your org |
arp-github-marketplace | GitHub Marketplace | Community-contributed agent cards via the GitHub Marketplace integration |
Your org may also have private ARP instances connected. There's no CLI command for listing registered ARPs specifically - rensei capacity provider list covers execution providers (where sessions run: e2b, Docker, local, etc.), a separate registry from Agent Registry Providers (where card definitions come from). Check your org's connected ARPs with your operator or via the platform API.
For the full ARP interface specification and how to implement a custom provider, see Agent Registry Providers.
Related pages
- Agent cards CLI -
rensei agent cardscommands - Agent cards overview - 4-scope model, YAML authoring, extends, versioning
- Agent Registry Providers (ARP) - provider interface, capability flags, custom registries
- Capacity providers -
capacity provider listto inspect registered ARPs