Skip to main content

Personas

LumenBazaar serves multiple audiences. Each audience needs a different path through the docs.

Seller​

A seller owns an API, model endpoint, data service, or MCP tool and wants to charge per call.

Seller needs:

  • Simple middleware.
  • Resource metadata helpers.
  • Pricing configuration.
  • Testnet onboarding.
  • Settlement receipts.
  • Dashboard visibility.

Seller reading path:

  1. Introduction
  2. Seller Guide
  3. Seller SDK
  4. Discovery Flow
  5. Testnet Guide
  6. Payments API Reference

Buyer​

A buyer is a developer, app, wallet, or automation service that wants to call paid resources.

Buyer needs:

  • Resource discovery.
  • Price and schema inspection.
  • Payment authorization.
  • Retry helper.
  • Receipts and error handling.

Buyer reading path:

  1. Introduction
  2. Buyer Guide
  3. Buyer SDK
  4. Payment Flow
  5. Discovery API Reference
  6. Facilitator API Reference

AI Agent Developer​

An AI agent developer needs agents to find paid tools and call them safely.

Agent needs:

  • MCP-compatible discovery tools.
  • Deterministic tool schemas.
  • Machine-readable errors.
  • Budget controls.
  • Receipts.

Agent reading path:

  1. Agent Guide
  2. MCP API Reference
  3. Discovery Flow
  4. Buyer SDK
  5. Paid MCP Tool
  6. Trust Model

Operator​

An operator runs the facilitator, discovery index, MCP server, worker, frontend, docs, and monitoring.

Operator needs:

  • Docker setup.
  • Environment configuration.
  • Network support.
  • Monitoring.
  • Key management guidance.
  • Maintenance docs.

Operator reading path:

  1. Operator Guide
  2. Self-Hosting
  3. Monitoring
  4. Runbook
  5. Incident Response
  6. Mainnet Guide

Contributor​

A contributor implements scoped tasks across frontend, backend, contracts, or docs.

Contributor needs:

  • Clear repository ownership.
  • Small issues.
  • Acceptance criteria.
  • Test requirements.
  • Pull request expectations.

Contributor reading path:

  1. Repository Map
  2. Repository Standards
  3. Issue Template
  4. Drips Contributor Plan
  5. Content QA

Reviewer Or Funder​

An SCF or Drips reviewer needs evidence that the project is real and useful.

Reviewer needs:

  • Working testnet demo.
  • Mainnet deployment plan.
  • Public repositories.
  • Clear milestones.
  • Test results.
  • Conformance reports.
  • Security posture.
  • On-chain metrics.

Reviewer reading path:

  1. Project Positioning
  2. Problem And Goals
  3. Architecture Overview
  4. Milestones
  5. Metrics
  6. SCF RFP Proposal
  7. Conformance Report Template

Security Auditor​

A security auditor reviews facilitator logic, catalog trust, MCP budget controls, contract behavior, operations, and evidence.

Auditor needs:

  • Trust boundaries.
  • Threat model.
  • Stable error codes.
  • Contract guarantees.
  • Generated references.
  • Test evidence.
  • Incident procedures.

Auditor reading path:

  1. Trust Model
  2. Threat Model
  3. Audit Readiness
  4. Facilitator API Reference
  5. Upto Session Contract
  6. Generated References
  7. Incident Response

Path Maintenance​

Update this page whenever:

  • New guides are added.
  • API or contract references move.
  • Mainnet support becomes live.
  • SDK packages move to a dedicated repository.
  • New reviewer or operator evidence pages are added.