Seller Guide — Creating & Setting Up Agents

This guide covers everything from becoming a seller to getting your first listing live. It's written for sellers who already know what they're building. If you picked the Hosted type and aren't sure how to deploy and connect your agent, read the Deployment Guide after this.

---

1. Pick the right listing type

AgentDukaan supports four ways to sell an agent. Choose based on who runs the agent after the sale.

Not sure? If you can't (or don't want to) run servers, avoid Hosted — sell as Source code, DFY, or Build-it guide instead. Hosted is the only type that requires you to operate live infrastructure.

The choice is made on Step 1 of the listing creator and drives which fields you see in the rest of the flow.

---

2. Become a verified seller (one-time)

You must do this once before you can submit any listing for review.

1. Become a seller — go to /sell. This upgrades your account to the seller role and creates your seller profile: display name, bio, expertise tags, portfolio links, and your response SLA.

2. Submit KYC — also on /sell. You provide:

   • PAN number (10 chars)
   • An identity document (Aadhaar / PAN / Passport)
   • Bank details — bank name, account number, IFSC (11 chars) — this is where payouts land.

   This sets your kycStatus to submitted. An admin reviews it (target: within 24 hours) and either approves or rejects with a reason.

You can build listings as drafts before KYC is approved, but you cannot submit a listing for QA until kycStatus = approved. A suspended account can't submit either.

Once approved you get a verification tier (verified → trusted → featured), which boosts your ranking in search and on the homepage.

---

3. Create the listing

Go to Seller Dashboard → New listing (/seller/listings/new). It's a 4-step wizard.

Step 1 — Type

Pick one of the four types above. You can't change the type after this without starting over.

Step 2 — Basics (all types)

Step 3 — Pricing & config

This is where the four types diverge.

Hosted

• Webhook endpoint (required, https in production) — AgentDukaan POSTs a notification here when a buyer finishes onboarding; your agent then pulls their credentials from a signed endpoint (secrets are never pushed to you). See the Deployment Guide for the exact contract.
  • Once live, your agent also reports each run (so monthly limits + usage work), can send an optional heartbeat, and can ask a buyer to re-enter a bad key — all in the Webhook & Callback Contract. Or have an AI add it all for you: Build & Verify Your Agent with AI.
• Free trial — 0 (no trial) or 1–30 days, no card required.
• Demo / booking link (optional) — adds a "Book a demo" button (e.g. a Calendly link).
• Pricing tiers — up to 3. Each has a name, a ₹/month price, an optional runs/month limit, and a feature list (one per line).
• Setup wizard — build the form the buyer fills in to configure the agent (see §5).

Source code

• Support days included — 0–90. How long the post-purchase support thread stays open.
• License options — up to 3 tiers, each single (1 deploy), multi (5), or unlimited (commercial), with a one-time ₹ price and a label.

Done-for-you (DFY)

• Calendly / booking link — for the discovery call.
• Languages supported — Hindi, English, Hinglish, Marathi, Gujarati, Tamil, …
• Packages — up to 3, each with a name, ₹ price, deliverables (one per line), delivery days, and revisions included.

Build-it guide

• What the buyer will build (outcome), target tool/editor, setup time, prompt count.
• What's inside and prerequisites (one per line).
• Support days and price tiers (Personal / Team / Commercial).
• The actual guide files (steps, prompts, PDFs) are added on Step 4.

When you click Save, the listing is created with status draft and you move to Step 4.

Step 4 — Files & demo video

• Build-it guide: the Guide Builder appears — add ordered steps, per-step files, and bonus resources. (See §6.)
• All types: upload a demo video (≤ 500 MB; mp4 / webm / mov / avi). A short demo is the single biggest conversion driver — buyers want to see it work before they pay. You can skip and add it later from the listing's Edit page.

---

4. Submit for QA → go live

A new listing is a draft and isn't visible to buyers. The lifecycle:

draft  ──submit──▶  pending_qa  ──admin approves──▶  approved (LIVE)
  ▲                                                      │
  └──────────────── edit (drafts/rejected only) ◀────────┘ pause ⇄ resume

1. From your dashboard, Submit for QA (PATCH /api/listings/:id/submit). Requirements: status is draft, your KYC is approved, and your account isn't suspended. Target review time: 48 hours.
2. An admin reviews on /admin/qa and either approves (status → approved, now live and discoverable) or rejects.
3. Pause / resume anytime once live — pausing hides it from buyers; resuming brings an already-approved listing straight back (no re-review).
4. Editing is only allowed on draft or rejected listings, and any edit drops the listing back to draft (so it must be re-submitted). You can't edit an approved listing in place — pause is for taking it offline, not editing.

---

5. The setup wizard (Hosted)

For hosted agents, the setup wizard is the form the buyer fills in to configure your agent (API keys, business name, language, limits, …). You build it in the listing creator with the Wizard Builder.

A wizard is a list of steps, each with fields:

Credential guides. A step that collects credentials can attach a guide so the buyer knows exactly how to create the secret. Either:

• pick a built-in provider (providerId) — we auto-render the official doc link, the exact permissions/scopes, and numbered steps. Built-ins include WhatsApp Business (Meta), Telegram Bot, IndiaMART, OpenAI, Anthropic, Razorpay, and Google service accounts; or
• supply a custom guide (your own instructions, permissions, doc URL) for a provider we don't have a template for.

Example (the WhatsApp Outreach Agent's first step):

{
  "version": "1.0",
  "steps": [
    {
      "id": "whatsapp",
      "title": "Connect WhatsApp Business",
      "description": "Enter your WhatsApp Business API credentials from Meta.",
      "guide": { "providerId": "meta_whatsapp" },   // auto-renders Meta's setup steps
      "fields": [
        { "id": "waba_phone",    "label": "WhatsApp Business phone number", "type": "tel",      "required": true, "sensitive": false },
        { "id": "waba_token",    "label": "WABA permanent access token",    "type": "password", "required": true, "sensitive": true  },
        { "id": "waba_phone_id", "label": "Phone number ID",                "type": "text",     "required": true, "sensitive": false }
      ]
    }
  ]
}

What the buyer enters here is exactly what your agent fetches from the signed config endpoint after they subscribe (sensitive fields are pulled per-run, never pushed to your webhook) — see the Deployment Guide.

---

6. Guide files (Build-it guide)

The Guide Builder (Step 4 / Edit page) lets you attach files to your playbook:

• Per-step files — files a buyer needs for a specific step (e.g. a prompt pack .md).
• Bonus resources — files not tied to a step (full PDF, licence, cheat-sheet).
• Limits: up to 100 MB per file; broad type allowlist (PDF, Office docs, text/markdown/CSV, JSON/YAML, zip/tar/7z, images, and octet-stream for misc configs like .env/.mcp).

Files upload directly to storage via a presigned URL; the platform issues each file's key inside your listing's private namespace, so a buyer only gets a signed, time-limited download after paying. Step prompt bodies and file links are never exposed in the public listing — buyers see step titles and a file manifest only.

---

7. Uploading the deliverable for Source-code listings

⚠️ Known gap — read before choosing the Source-code type.

The data model has a codebaseR2Key (the downloadable .zip) and setupDocsR2Key (a setup PDF) for source-code listings, and the buyer's download flow reads from them. But there is currently no UI or API endpoint to upload that zip yourself — only the demo-video and guide-file uploads are wired into the product. Today a source-code deliverable is attached out-of-band (seed script / admin). If a buyer tries to download before it's attached, they get "File not yet uploaded by seller."

If you want a self-serve "sell downloadable files" flow that works end-to-end today, use the Build-it guide type — it reuses the same one-time-purchase + signed-download plumbing and does have a working file uploader (the Guide Builder). Otherwise, coordinate with the platform to attach your source zip.

---

8. Pricing, fees & payouts

Affiliate bonus: drive your own traffic with your referral code and earn an extra 5% of gross on top of your normal cut (30-day attribution).

Trust & ranking. Listings are ranked by a blend of (Bayesian-adjusted) review quality, sales traction, your verification tier, responsiveness, review volume, and freshness. Keep your response SLA low, gather genuine reviews, and keep listings fresh to rank higher. Reaching ≥5 sales and a ≥4.5 rating with approved KYC promotes you to Trusted.

---

9. Quick checklist

• Account upgraded to seller + KYC approved
• Listing type chosen to match who runs the agent post-sale
• Name (3–60), tagline (10–120), description (≥50 chars), category set
• India integrations tagged (buyers filter on these)
• Pricing tiers / license options / packages configured
• Hosted: webhook endpoint set + tested, setup wizard built → see Deployment Guide
• Build-it guide: steps + files added in the Guide Builder
• Demo video uploaded
• Submitted for QA (drafts re-enter draft on any edit)