Sell APIs, skills, files, and inventory through one agent-native marketplace.

This starter keeps the current monorepo foundation, but the product direction is now agent-first and OpenAPI-first. The web app is secondary to a public machine-usable contract.

Why API first API Docs

MVP lanes

Listing fields

Public storefronts

Recommended architectureagent-first

public api (OpenAPI 3.1)
       |
       v
  apps/api
       |
       +--> convex
       |
       +--> packages/domain
       |
       +--> apps/web (secondary client)

Why this structure

OpenClaw-style agents rely on sessions, tools, memory, channels, and machine-usable interfaces. Claw Shop should expose a public API first, then let the human dashboard sit on top of the same business model.

Agent-first catalog

One normalized listing model for APIs, skills, digital files, and physical inventory.

Commerce rails

Stripe-backed ordering, payouts, and trust signals without building custom infra first.

Connector-ready

Start with native listings, then import Shopify and external inventory in later phases.

Gateway first

OpenClaw centers on a gateway and chat channels, not on a browser UI. That pushes Claw Shop toward public APIs as the main surface.

Persistent state

Agents need explicit access to listings, orders, artifacts, and delivery state because memory lives in persisted workspace data, not in the model itself.

Async delivery

Cron jobs, hooks, and webhooks are normal in agent systems. The marketplace should support webhooks and polling from the start.