Skip to content

Publishing Your Agents

The Traylinx Marketplace lets builders publish AI agents and earn revenue from usage. Agents can be built inside projects and, when compatible, run on Tytus private pod infrastructure.

Requirements

  • You need an active Traylinx account.
  • Your agent must belong to a project.
  • Your agent should have a clear purpose, working configuration, and safe credentials.
  • Publishing requires Creator or Operator.

Plan limits: - Explorer: no marketplace publishing. - Creator: 1 professional agent listing, 70% creator share. - Operator: up to 1000 professional agent listings, 85% creator share.

Publish an agent

  1. Open the project that contains the agent.
  2. Open project settings or the agent publishing flow.
  3. Click Publish to Marketplace.
  4. Add title, description, category, pricing model, and usage price.
  5. Review the listing.
  6. Click Confirm & Publish.

Use plain, specific copy. Tell users what the agent does, what inputs it needs, and what result they get.

Update a listing

  1. Open the project.
  2. Open the published agent listing.
  3. Click Update Marketplace Listing.
  4. Save changes.

Unpublish a listing

  1. Open the project.
  2. Open the published agent listing.
  3. Click Unpublish.

The listing returns to draft. Existing active sessions may continue until they finish.

Tytus and first-party agents

OpenClaw and Hermes are first-party Famous Agents and are managed from the Tytus page, not through normal marketplace publishing.

Use Tytus to: - Check which plan supports each agent. - Open agent landing pages. - Connect your pod. - Generate env blocks and references.

Common blockers

  • Publish button disabled: upgrade to Creator or Operator.
  • Listing limit reached: upgrade to Operator.
  • Credentials missing: add project API keys or Sentinel Pass credentials.
  • Agent rejected: improve description, safety, stability, or category fit.

Mirrored from traylinx-web:docs/user-manuals/agent_publishing.md. Edit the source in the traylinx-web repo — changes here are overwritten by the sync script.