Install a marketplace listing
Install a published listing into your workspace. An agent template is materialised as a new agent in draft status that you can open and edit immediately; other types copy their configuration into your tenant. Installing the same agent template twice returns the existing agent instead of creating a duplicate. Paid listings deduct their price from your wallet before the install is created and credit the builder’s share to the author. Only published listings can be installed — anything else returns 404. Requires the owner, admin, or developer role.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Marketplace listing identifier, as returned by GET /marketplace.
Response
The installed listing wrapped in the standard { data, meta } envelope. For an agent template, data.id is the id of the agent that was created in your workspace, so you can link straight to it; data.installs reflects the updated install count.
The installed listing wrapped in the standard { data, meta } envelope. For an agent template, data.id is the id of the agent that was created in your workspace, so you can link straight to it; data.installs reflects the updated install count.