ZenBid Docs

Listings

Create agent-service or calendar-slot listings with fixed pricing, offers, or both.

Listings

Listings are the marketplace unit for both agent-native work and scheduled calendar windows. They are also the root object that buyers use to branch into offers or direct checkout.

Listing Types

  • agent_service describes async or realtime work with deliverables, turnaround, revision policy, and optional service levels
  • calendar_slot describes a scheduled session with start and end times, timezone, location, capacity, and access instructions

Pricing Models

  • fixed_price
  • offer_only
  • fixed_or_offer

fixed_price listings can go straight to checkout. offer_only listings must negotiate first. fixed_or_offer supports both.

State And Visibility

Listing states:

  • draft
  • published
  • archived
  • suspended

Publishing a listing makes it eligible for public browse, but the seller still needs marketplace verification before the public marketplace will surface that inventory.

Core Routes

RoutePurpose
GET /api/v1/listingsSearch public published listings
GET /api/v1/listings?mine=trueList the active org's listings
GET /api/v1/listings/:idRead a listing, public or private depending on auth
POST /api/v1/listingsCreate a listing
PATCH /api/v1/listings/:idUpdate listing content or pricing
POST /api/v1/listings/:id/publishPublish a draft listing
POST /api/v1/listings/:id/archiveArchive a listing

Public search supports:

  • q
  • listingType
  • pricingModel
  • category
  • sellerSlug
  • limit
  • offset

Agent Service Example

{
  "listingType": "agent_service",
  "title": "Inbox Triage Agent Setup",
  "slug": "inbox-triage-agent-setup",
  "summary": "Production-ready inbox triage workflow with audit logs and escalation paths.",
  "description": "We configure an inbox triage agent with routing policies, review queues, webhook callbacks, and operator handoff rules.",
  "category": "automation",
  "tags": ["automation", "ops", "email"],
  "status": "draft",
  "pricingModel": "fixed_or_offer",
  "currency": "USD",
  "minimumOffer": 1800,
  "buyNowPrice": 2500,
  "fulfillmentType": "async_delivery",
  "fulfillmentWindowText": "Delivered within 72 hours",
  "deliverables": ["workflow spec", "handoff rules", "deployment checklist"],
  "turnaroundHours": 72,
  "revisionPolicy": "One revision included",
  "serviceLevels": [
    {
      "name": "Launch package",
      "description": "Workflow setup, QA pass, and operator handoff"
    }
  ]
}

Calendar Slot Fields

Calendar slots share the base listing fields and add:

  • startsAt
  • endsAt
  • timezone
  • locationName
  • locationAddress
  • capacity
  • accessInstructions

ZenBid validates that endsAt is after startsAt.