Skip to main content

Marketplace

Marketplace brings together reusable resources for different jobs: policy checkpoints, Service/Rental/Stint flow templates and snippets. Each resource has its own adoption path. Selecting a flow template, saving a policy and deploying it to a robot are different actions.

Marketplace​

Start from a resource that matches your task, then inspect what still needs configuration. A useful example is a Stint intake flow: the template supplies a connected graph, while your business must provide the actual intake form and operating requirements.

Copy a flow template​

  1. Open Marketplace and find Service Templates, Rental Templates or Stint Templates.
  2. Review the template name, description, preview and node count. Read validation messages inside the preview; a graph can have connections while still missing a form or pricing tier.
  3. Choose the template's Select action. The current workflow creates a new local draft and opens it in the flow editor.
  4. Rename the copy and inspect its nodes, connections and settings. Replace example resources with the intended published forms, tiers and business configuration.
  5. Save and reopen the draft. Resolve the editor's errors before connecting it to an offering or publishing it.

The reviewed Stint Work Order template created a three-block local flow. Its copy was renamed “Workshop inspection intake — rehearsal,” saved and reopened, then selected in a Stint setup draft:

Stint setup showing the locally adopted Workshop inspection intake flow selected with three blocks and two connections
Adoption produced a selectable local copy. The Stint setup was cancelled; neither the offering nor the flow was published. The copied template still needed a published form before use.
Stint setup showing the locally adopted Workshop inspection intake flow selected with three blocks and two connections

Adoption produced a selectable local copy. The Stint setup was cancelled; neither the offering nor the flow was published. The copied template still needed a published form before use.

Template cards can contain missing-resource messages. The inspected copy showed a Work Order Form without a selected form, one error and an unavailable Next action. Adoption therefore verified the editable starting point, not a completed customer submission or operational workflow.

Inspect and save a policy checkpoint​

Open a policy listing to review its description, supported robot model and checkpoint versions. Inspect the selected version's report, configuration and available preview before saving it. A saved checkpoint can be found through the policy workflow; it does not automatically install or execute on a Servo.

In the inspected Basic Walking listing, version 1.1.1 and its checkpoint controls loaded, but the policy preview reported Failed to load policy / Failed to fetch. No working simulation or physical behavior is claimed, and no empty failed preview is used as a product demonstration. Saving, deploying and running that checkpoint were not exercised.

See Policies, Simulator and Servos for the separate preparation and device requirements. Compatibility and a successful preview matter more than a listing's name or promotional description.

Save a snippet​

Snippet listings offer their own Save action. Review what the snippet does and any required Bank before using it. A saved snippet is a reusable resource, not proof that its connected data, permissions and actions are configured. See Snippets for setup and testing.

Share a resource​

Add New Listing starts a sharing workflow for a policy, snippet or flow template. Review ownership, attached resources and visibility before confirming. Do not publish a listing containing private business data or credentials. No listing was created or shared during this review.

Troubleshooting​

  • Search does not show a template: clear the query and inspect the template sections; the inspected search filters policy listings while the template sections are shown without a search query.
  • Copied flow is incomplete: configure its actual missing forms, tiers or other resources in the editor. A node count does not validate the workflow.
  • Policy preview fails: inspect the error and resource availability before attempting adoption or deployment. A loaded version label is not a loaded policy.
  • Saved resource is not useful yet: open the destination feature and check dependencies, permissions and compatibility.

Related guides: Flows, Stint Flows, Services and Rentals.