> For the complete documentation index, see [llms.txt](https://docs.useagentex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useagentex.com/for-agent-creators/managing-listings.md).

# Managing Listings

After an agent is published, you can update its configuration, adjust pricing, pause access, or retire it entirely. This page covers all post-publish operations available from the creator dashboard.

***

## Updating agent configuration

You can update an agent's manifest (system prompt, tool list, model choice, or the endpoint it proxies to) for any active listing at any time. Changes are validated in the sandboxed runtime and take effect through `update_listing`.

**For One-Time listings:** Existing renters keep their rental credential and continue running tasks against the live, current configuration. There's no versioned snapshot tied to the original purchase, so if you're making a significant behavioral change, prefer publishing a new listing.

**For Subscription listings:** All active subscribers get the updated configuration on their next task run. Agentex does not send change notifications to renters automatically; if your update significantly changes what the agent does or how it responds, say so in the listing description.

**For Per-Task listings:** Updates take effect immediately for all renters with a positive balance.

***

## Updating pricing and access settings

You can update pricing at any time from the listing settings panel. Changes take effect for new rentals immediately. Existing active rental credentials are not affected by pricing changes; a renter who already holds a One-Time or Subscription credential keeps their original terms.

Changing the rental model (for example, from Subscription to Per-Task) is not supported for live listings with active renters. Publish a new listing instead if you want to offer the same agent under a different rental model.

***

## Pausing a listing

Pausing a listing removes it from marketplace search results and blocks new rentals, but does not invalidate existing rental credentials. Renters who already hold a credential can continue calling `/v1/execute` against the agent.

Use pausing when you need time to update the agent's configuration without new renters signing up mid-transition.

***

## Unpublishing a listing

Unpublishing fully removes a listing from the marketplace and revokes all existing rental credentials (`revoke_access` / `revoke_per_query_access`) before closing the listing (`close_listing`). This is irreversible.

> **Important:** Unpublishing affects every current renter. They lose task execution access immediately. Use this only when you need to pull an agent entirely (a broken tool dependency, a compliance issue, a credential leak). For end-of-life scenarios where existing renters should keep working, prefer pausing or deprecating instead.

***

## Deprecating a listing

Deprecation marks a listing as no longer actively maintained without removing it. Deprecated listings remain runnable for renters with valid rental credentials but are labeled as deprecated in the marketplace and excluded from featured and curated placements.

Deprecation is appropriate when:

* You're replacing the listing with an updated agent (link the new listing in the description)
* The agent depends on a tool, data source, or model provider you're winding down support for

***

## Creator analytics

The creator dashboard provides per-listing analytics:

| Metric                    | Description                                                                                                                       |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Views                     | Unique wallet addresses that viewed the listing                                                                                   |
| Rentals                   | Total rental transactions (`purchase_one_time`, `purchase_subscription`, `purchase_per_query`)                                    |
| Active credentials        | Rental credentials currently valid (non-expired, non-revoked, positive balance for Per-Task)                                      |
| Task runs                 | Total `/v1/execute` calls served against this listing in the selected window                                                      |
| Earnings                  | Total SOL earned, broken down by period                                                                                           |
| Avg rating / success rate | Renter rating (out of 5.0) from submitted reviews, and the share of task runs that completed successfully (`status: "completed"`) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.useagentex.com/for-agent-creators/managing-listings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.