Skip to main content

​
Choose and prepare an agent marketplace template

Use the agent marketplace to find a prebuilt template for a defined task, then adapt and evaluate it in your workspace. A listing is a starting configuration, not a guarantee that it fits your policies, tools, or traffic. Inspect its prompt and prerequisites before installing.

​
Browse and inspect

Open Agents → Marketplace and search or filter the catalog. The live catalog is authoritative; available templates and categories can change. Select a listing to review its description, channels, prompt, model, and tools. Published configuration is public, so never include API keys, webhook secrets, or customer records in a listing. An installed template is a copy in your organization, not a live link to the publisher’s listing. Changes to the original do not update the copy. For the API sequence, see Browse, install, and publish marketplace templates.

​
Install and evaluate in a sandbox

Install the listing through the marketplace or dashboard. An agent template creates a new agent in draft status; open that agent and review the configuration before enabling it. Configure the tools, knowledge, channels, guardrails, and escalation behavior your use case requires. Use a sandbox or test key before live traffic. Run representative scenarios with persona simulation, then save fixed cases in the simulation and regression eval suite to compare prompt changes. Simulation evidence applies to the scenarios and rubric you ran; it is not a universal quality certification. Set your workspace’s tenant-owned governance and spend limits before deployment. See Agent governance policies and Agent cost controls. A passing test does not prove the configuration will fit every live conversation or stay within an unspecified cost.

​
Stage and monitor a release

Save a version of the configuration you evaluated. Use a canary rollout where available to increase traffic in stages and watch its quality signals. If the candidate regresses, roll it back or promote the prior saved version. Promotion of an older version creates a new version record, preserving the change history; it cannot reverse actions already taken with customers. During live operation, use Live conversation monitor to inspect active conversations and intervene when an agent needs human direction. Keep monitoring and escalation paths in place even when a canary advances.

​
Publish a template

Create an agent_template listing with a specific name, useful description, and configuration. Explain the task boundary, tools and setup required, intended channels, and cases that should be handed to a person. Keep secrets and private data out of the listing because published configuration is publicly readable. Build evidence before you submit: exercise varied customer behavior with persona simulation and use a fixed regression suite after prompt changes. Describe only the scenarios you ran and results you observed. The marketplace does not issue an automatic evaluation badge or promise a moderation turnaround. Submit the listing for review and track its status; it becomes visible only after approval. If rejected, use the review note to revise and resubmit. For the full listing-state and review details, read Marketplace listing lifecycle and Moderate agent template submissions. A paid install deducts the installer’s charge before creating the copy. If creation fails, the platform attempts a compensating refund, but the refund is best-effort; a failed installation can leave a charge that needs follow-up. Builder payout is a separate best-effort operation after a successful install, so a payout failure does not undo the installed agent. Do not assume the charge, copy, and payout form one atomic transaction. After a paid install, verify the resulting agent and wallet activity; contact support if the installation or charge does not match.

​
Frequently asked questions

​
Who owns PII in a marketplace template?

A published listing contains configuration, not a buyer’s private workspace conversations. The buyer’s installed copy is in the buyer’s workspace. Keep PII and credentials out of public listing configuration, and configure your own tenant’s access, retention, and PII controls for the installed agent.

​
Can I roll back a marketplace agent?

Yes. Save versions before deployment. Promote the prior saved version to restore its configuration; the rollback creates a new version record. For an active canary, roll back the candidate to remove it from traffic.

​
Is outcome pricing included with a paid listing?

No. A listing’s install price, when set, is separate from outcome-based agent billing. Outcome charging is a separate tenant-controlled opt-in and applies only when an evaluated conversation passes the configured rubric. See Outcome-based AI-agent billing.