> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a Market

> Create a governed exchange for listings, fulfillment flows, verification, and settlement.

## Build a Market

A Market is a trusted exchange layer. It helps participants discover, offer, request, verify, and settle services, assets, data, protocols, claims, outcomes, credentials, or agent capabilities.

Build a Market when multiple parties need a governed way to find each other, transact, prove fulfillment, and settle value.

<Card title="Market Builder" icon="wand-magic-sparkles" href="#add-market-builder-url" cta="Build with AI" arrow={true}>
  Use the Market Builder Agentic Oracle in qi.space to turn your exchange model, participants, listings, verification rules, and settlement logic into a market design.
</Card>

### What you will create

* Market purpose and operating model
* Listing types
* Supplier and buyer roles
* Eligibility and onboarding rules
* Pricing, fees, rewards, or settlement model
* Fulfillment Flow
* Verification Blueprint
* Reputation and credential rules
* Dispute and refund handling
* Governance and moderation rules
* Analytics and learning loops

### Quick start

<Steps>
  <Step title="Define what is exchanged">
    Decide what participants can list, request, purchase, fund, verify, or subscribe to. Examples include services, agents, datasets, credentials, protocols, projects, claims, or verified outcomes.
  </Step>

  <Step title="Define the market actors">
    Identify suppliers, buyers, funders, verifiers, operators, governors, agents, and external services. Assign what each actor can do.
  </Step>

  <Step title="Design the listing model">
    Specify listing fields, eligibility requirements, pricing, availability, service-level expectations, evidence requirements, and fulfillment terms.
  </Step>

  <Step title="Attach fulfillment flows">
    Choose the Flow that runs after a listing is requested, ordered, funded, assigned, delivered, verified, disputed, or settled.
  </Step>

  <Step title="Attach verification blueprints">
    Use a Blueprint to define how fulfillment is proven, who verifies it, what evidence is acceptable, and what happens after approval or rejection.
  </Step>

  <Step title="Configure settlement">
    Define how value moves. Include payments, fees, rewards, escrow, outcome-based release, credits, reputation updates, or credential issuance.
  </Step>

  <Step title="Pilot with a controlled cohort">
    Launch with a small group of trusted suppliers and buyers. Measure discovery, conversion, fulfillment quality, verification time, disputes, and settlement success.
  </Step>
</Steps>

### Useful first scope

Start with a market that has:

* one listing category
* one supplier type
* one buyer type
* one fulfillment Flow
* one verification Blueprint
* one settlement rule
* one dispute path

### Resources

<CardGroup cols={2}>
  <Card title="Blueprints" icon="diagram-project" href="/blueprints/markets">
    Start from marketplace templates for verified services, outcome funding, protocol exchange, agent services, datasets, or credentialed suppliers.
  </Card>

  <Card title="Concepts" icon="store" href="/concepts/markets">
    Learn how Marketplaces connect listings, participants, credentials, flows, protocols, verification, pricing, settlement, and reputation.
  </Card>

  <Card title="Code with AI" icon="terminal" href="/guides/markets/code-with-ai">
    Generate listing schemas, marketplace configuration, fulfillment workflows, verification logic, and settlement test cases with an AI coding assistant.
  </Card>

  <Card title="Deep dive" icon="book-open" href="/guides/markets/deep-dive">
    Understand marketplace architecture, trust models, liquidity design, verification, governance, settlement, and operations.
  </Card>
</CardGroup>