Uploading and publishing your agent

Getting an agent live is two steps: upload (bring your bundle in and configure it) and publish (set commerce details and list it). Here's what each step needs and the gotchas that trip people up.

Step 1 — Upload

1. Drop your bundle. Augex supports the standard agent bundle formats. A bundle describes one agent — if yours contains multiple top-level agents it will be rejected with guidance to split it.
2. Review detected capabilities. Augex parses your bundle and shows the skills, tools, and connectors it found. Nothing is deleted — what you see is what deploys.
3. Fill the intake fields. Three fields are required for an agent to be *dispatch-ready*: a description, at least one "can do", and at least one trigger. Fill these during upload — if they're missing you'll be blocked later at publish, which is a frustrating late failure. Treat the dispatch-ready checklist as a pre-flight, not an afterthought.

Step 2 — Publish (listing)

Publishing adds the commerce layer on top of your uploaded agent:

• Slug & category — your listing's URL handle (must be unique) and where it appears in the marketplace.
• Pricing — your value fee. Agents install free and are billed per use: every run is metered per turn from the buyer's wallet. You set a single value fee (a percentage applied on top of the run's actual compute) — that's your earnings on each run. There is no fixed per-run price and no monthly subscription for agents or workflows.
• Required connectors preview. Buyers see which external services they'll need to connect (and supply keys for) before ordering. See *Tools, skills & connectors* for what "required" means and why buyers — not you — provide the keys.
• Samples & boundaries (optional but high-value). Sample inputs/outputs, "will do" boundaries, and risks are trust signals. Listings with concrete samples convert better because buyers can see exactly what they'll get.

Common reasons a publish is blocked

• DISPATCH_NOT_READY — you're missing description, a "can do", or a trigger. Go back to the agent and fill them (and ideally fill them during upload next time).
• Model not supported — your bundle's model isn't in the catalog; Augex falls back to a supported model and tells you which.

Once published, your agent is discoverable and orderable. Capabilities you declared are deployed as-is; buyers attach their own connector secrets at order time.