mercurjs.com valid

MercurJS Documentation

Mercur is the open-source enterprise marketplace platform. Composable, API-first, and AI-native, it runs on your own infrastructure with role-based access control, an auditable change pipeline, and full code ownership. It powers multi-vendor sellers, commissions, order splitting, and payouts, with an admin panel and a vendor portal, on a proven Medusa commerce core.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T08:11:18.548Z. Cached copy · Source on mercurjs.com

# MercurJS Documentation

> Mercur is the open-source enterprise marketplace platform. Composable, API-first, and AI-native, it runs on your own infrastructure with role-based access control, an auditable change pipeline, and full code ownership. It powers multi-vendor sellers, commissions, order splitting, and payouts, with an admin panel and a vendor portal, on a proven Medusa commerce core.

- [Mercur Documentation](https://docs.mercurjs.com/home.md): The open-source enterprise marketplace platform. Composable, API-first, and AI-native, on infrastructure you own.
- [Overview](https://docs.mercurjs.com/learn/introduction.md): Set up Mercur, tour the operator and seller panels, and see how a multi-vendor order flows.
- [Why Mercur](https://docs.mercurjs.com/learn/why-mercur.md): Why teams choose Mercur to run an enterprise marketplace: governance, ownership, and composability without a closed platform.
- [Use cases](https://docs.mercurjs.com/learn/use-cases.md): Two ways to run Mercur: as the whole marketplace, with its own storefront, admin and vendor panels, or as the marketplace layer inside a store you already run, selling seller offers next to your own products.
- [Building with AI](https://docs.mercurjs.com/resources/ai/overview.md): Mercur ships version-matched docs inside your project so AI coding agents build from accurate APIs instead of stale training data.
- [Skills](https://docs.mercurjs.com/resources/ai/skills.md): Agent skills for building on Mercur: the bundled-docs contract plus the official Medusa agent skills.
- [MCP Server](https://docs.mercurjs.com/resources/ai/mcp.md): Connect your AI environment to Mercur documentation via Model Context Protocol.
- [Architecture](https://docs.mercurjs.com/learn/architecture.md): What runs where in a Mercur project, which package does what, and where your own code goes.
- [Migration to 2.0](https://docs.mercurjs.com/learn/migration-to-2-0.md): Port an existing Mercur 1.x project to 2.x, the latest release.
- [Telemetry](https://docs.mercurjs.com/telemetry.md): Learn about the anonymous usage data collected by the Mercur CLI
- [Stores](https://docs.mercurjs.com/platform/store/overview.md): Control who sells on your marketplace, who works on each store, and when a store can trade.
- [What a store is made of](https://docs.mercurjs.com/platform/store/concepts/store-entity.md): The seller record, its currency and regions, and the satellite records that hold its business details.
- [How store teams work](https://docs.mercurjs.com/platform/store/concepts/team.md): Members, memberships, owners, roles, invites, and how a member picks the store they act for.
- [Store statuses and transitions](https://docs.mercurjs.com/platform/store/concepts/lifecycle.md): The four store statuses, the workflow behind each transition, scheduled closures, and the premium flag.
- [Create a store from server code](https://docs.mercurjs.com/platform/store/guides/create-a-store.md): Create stores with createSellersWorkflow
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=mercurjs.com · GET /v1/domain/mercurjs.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mercurjs.com:
1. POST https://agentwebmap.com/v1/sites/mercurjs.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://mercurjs.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/mercurjs.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mercurjs.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.