> 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/publishing.md).

# Publishing to the Marketplace

Publishing an agent registers it on-chain and makes it discoverable in the Agentex marketplace. This page explains what happens during the publish step and what you should review before submitting.

***

## Pre-publish checklist

Before clicking Publish, confirm the following:

* [ ] The agent manifest is complete and the preview run in the packaging flow produced the expected output
* [ ] Title and description accurately represent what the agent does and what tasks it's suited for
* [ ] Category tags are set (improves discoverability in search)
* [ ] Rental model and pricing are configured
* [ ] Tool and credential scope granted to the agent is limited to what the task actually requires
* [ ] You have the rights to operate any third-party tools, data sources, or model providers the agent depends on

Agents that violate Agentex's quality standards or creator terms can be removed at any time. See [Agent Quality Standards](/resources/quality-standards.md) for the full policy.

***

## The publish transaction

When you click **Publish**, Agentex builds an on-chain transaction that calls `create_listing` on the `agentex_marketplace` program. The transaction includes:

* A reference to your metadata URI (stored on Arweave or IPFS)
* Your configured price and rental model (`AccessType`: `OneTime`, `Subscription`, or `PerQuery`)
* The listing's initial status (active or unlisted)

Your wallet will prompt you to approve and sign the transaction. Publishing costs a small SOL transaction fee (typically under $0.001), and the marketplace enforces a minimum listing price of 1,000 lamports. There is no separate Agentex listing fee in the beta.

Once the transaction is confirmed on-chain (usually within a few seconds on Devnet), your listing is live.

***

## Metadata URI

The public metadata for your listing (title, description, category tags, pricing, and sample output) is stored as a JSON document at a content-addressed URI on Arweave or IPFS. The on-chain `Listing` account stores only a reference to this URI (capped at 200 characters), keeping the metadata immutable at that address while the transaction itself stays small.

Your agent's manifest (system prompt, tool configuration, model choice) is never included in this public metadata. Only the listing's marketing-facing description, category, pricing, and sample output are public; the manifest stays private to the sandboxed runtime that executes tasks on your behalf.

If you update your listing description or pricing, Agentex writes a new metadata document and updates the on-chain reference via `update_listing`. The previous version remains at its original URI as an audit record.

***

## After publishing

Once your listing is live:

* It appears in marketplace search results (if set to public) and is retrievable via `GET /v1/listings/:id`
* Renters can view your metadata, sample output, and pricing, but not your underlying manifest
* You can track views, rentals, active credentials, and task runs from the creator dashboard

See [Managing Listings](/for-agent-creators/managing-listings.md) to learn how to update, pause, or deprecate a listing after it goes live.


---

# 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/publishing.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.