Publishing converts a private agent into a shareable agent that others can install against their own services.

Prerequisites

• At least one agent in your Gazebo account

Publishing from the dashboard

1. Open Agents in the Gazebo dashboard
2. Click Publish agent in the top right
3. Fill in the publish dialog:
   • Source agent — pick which of your existing agents to publish as the template
   • Name — human-readable, clear what the agent does (e.g. "Stripe Payment Monitor")
   • Description — one to three sentences explaining what the agent does and why someone would install it. Write for a non-technical user.
   • Slug — the URL path for the install link (e.g. stripe-payment-monitor → gazebohq.com/install/stripe-payment-monitor)
   • Declared scope — add each service the agent needs and which actions it requires (read, write, create, update, delete, or * for all). This is what installing users will see on the consent screen.
4. Click Publish

Gazebo creates a versioned identity snapshot and generates:

• install_url — gazebohq.com/install/<slug>
• verify_url — gazebohq.com/agents/verify/<slug>

The shareable link

The install URL is what you share. Add it to your README, marketplace listing, or documentation:

https://gazebohq.com/install/stripe-payment-monitor

When someone clicks this link, they land on the consent screen — a full view of what you're requesting, with no ability for you to see what they grant.

Defining the scope

The declared scope is the set of services and actions the agent will request when users install it. Be specific — requesting only the permissions the agent actually needs builds trust with installing users.

Action	HTTP methods	When to use
read	GET	Reading or listing data
write	POST, PUT, PATCH	Creating or updating data
create	POST	Creating new records only
update	PUT, PATCH	Updating existing records only
delete	DELETE	Deleting records
*	All	Full access (use sparingly)

What you can and cannot do after publishing

You can:

• View install count and status from the Published agents section
• Revoke the published agent (stops new installs; existing install tokens continue working until the user revokes them)
• Publish a new version with updated scope

You cannot:

• Edit the declared scope of the current version
• See who installed your agent or what services they've connected
• Access or retrieve any credentials from an installing user's vault

Publishing a new version

If your agent needs additional permissions, publish a new agent with the updated scope. Existing installs continue working under the original scope — users choose whether to install the new version.