Marketplace

rensei marketplace lets you discover agent configurations published to the Rensei Agent Registry. Browse by work type or provider - a marketplace card must be promoted into a project's Agent Cards before rensei dispatch can name it (see Dispatching an agent from the marketplace below).

CommandCopy Anchor Link

marketplace browseCopy Anchor Link

Browse available agents in the Agent Registry.

rensei marketplace browse \
  [--work-type <type>] \
  [--provider <id>] \
  [--json]

# 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 --json

Example 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.3

Example 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 marketplaceCopy Anchor Link

dispatch names a card the project can dispatch - its slug, its display name, or its agent:// reference - not a raw marketplace card ID. To make a marketplace card dispatchable 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), then dispatch by the promoted card's name:

rensei dispatch <card> --project my-fintech-app --goal "<free-text goal>" --wait

See Agent cards CLI and Agent cards overview for the full card resolution model.

Agent Registry Providers (ARP)Copy Anchor Link

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:

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 pagesCopy Anchor Link

• Agent cards CLI - rensei agent cards commands
• Agent cards overview - 4-scope model, YAML authoring, extends, versioning
• Agent Registry Providers (ARP) - provider interface, capability flags, custom registries
• Capacity providers - capacity provider list to inspect registered ARPs