Skip to content

Public Hubs

Public hubs are shared hubs listed for discovery. They are useful for learning Thalovant, trying examples, and connecting Free-plan clients before creating your own hubs.

You can use a public hub without owning that hub. The hub owner manages the hub, skills, and runtime. You create your own client and keep that client’s permissions narrow.

For the full route, see the public hub scenario.

If you are brand new, public hubs are the safest first path because you can learn the client and permissions flow without creating your own hub.

  • you are exploring Thalovant for the first time;
  • you want a Free-path setup before creating an owned hub;
  • you need a public hub client path with narrow access;
  • you want starter prompts before deciding what to build.
Public hubs screen showing filters, quality labels, audience guidance, starter prompts, and the client path.
Public hub listings help you choose a shared hub, create one client, and keep permissions narrow.

Public hub listings can include:

  • title and description;
  • quality label;
  • community label;
  • audience category;
  • age guidance;
  • tags;
  • starter prompts.
CertifiedGeneral13+Public hub

Starter prompts show what the hub is designed to handle. You can copy a prompt or try it when live preview is available for that hub and your plan has remaining preview allowance.

Good starter prompts are:

  • short;
  • plain language;
  • free of links or markup;
  • clearly related to the hub purpose.
  1. Choose a public hub. Use filters for quality label, audience, age guidance, and tags.
  2. Read the listing. Check the description, audience, starter prompts, and any quality label.
  3. Create a client. The client connects to the chosen public hub.
  4. Use narrow access. Public hub clients are designed for safe question-style access first.
  5. Review Billing when you need more. Move toward an owned workspace when you need private hubs, more clients, separate skills, or runtime config.

Stop after one public hub client and confirm the client exists with narrow permissions. That first pass teaches the same pattern you will use for owned hubs later.

ChoiceYou manageGood for
Public hubYour client and permissions.Learning, trying examples, and Free-path exploration.
Owned hubHub, skills, runtime config, clients, and permissions.Private workspace experiences and team-controlled setup.

A public hub setup looks right when:

  • the listing explains what the hub is for;
  • audience and age guidance fit your use;
  • the client name explains the purpose;
  • permissions are narrow;
  • Dashboard shows no unexpected attention item.