> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/concepts/knowledge-commerce.md).

# Knowledge Commerce

A participant may contribute valuable knowledge, specialize in graph reasoning, or offer a model that helps others analyze the graph. Knowledge commerce is the direction in which those contributions and capabilities become services other participants can discover and pay to use.

The DKG gives this exchange a shared knowledge structure, attributable participants, and provenance that consumers can inspect. An agent could combine a graph query from one provider with analysis from another, then retain the sources behind the result. The service and payment workflows are under development.

For the broader public direction, see the [NeuroSymbolic Marketplace RFC](https://github.com/OriginTrail/OT-RFC-repository/tree/main/RFCs/OT-RFC-27_NeuroSymbolic_Marketplace) and [feature availability](/references/availability.md). The RFC covers knowledge and inference services; x402 is a separate payment integration direction, not a synonym for the marketplace.

## A possible paid-access exchange

```mermaid
sequenceDiagram
  participant Buyer as Buyer agent
  participant Gateway as Serving node
  participant CG as Context Graph
  participant Chain as Verifiable Memory

  Buyer->>Gateway: Request gated knowledge
  Gateway->>Buyer: Quote or payment requirement
  Buyer->>Gateway: Payment proof
  Gateway->>CG: Authorize access or issue grant
  Gateway->>Buyer: Return graph data + provenance
  Buyer->>Chain: Verify UAL / commitment when available
```

## Current status

The public roadmap describes knowledge-service and context-oracle directions, and the codebase includes payment-proof and x402-related hooks. The diagram illustrates a possible paid-access exchange; it is not the complete marketplace settlement design or a released endpoint contract. Use the [roadmap](/concepts/roadmap-and-convergence.md#knowledge-and-intelligence-services-across-the-network) for the broader service direction and prototype evidence.

Current DKG V10 users should rely on:

* Working Memory for private local drafts
* Shared Working Memory for peer-visible collaboration
* Verifiable Memory for on-chain finality
* Context Graph access policy for scoped collaboration

## x402

x402 is an HTTP payment pattern for agent-to-agent or client-to-service payments. In the V10 roadmap, it is a possible way to pay for knowledge endpoints and premium graph data. A usable integration will need the serving node's supported endpoint, access policy, payment requirements, and verification procedure.

Until then, do not build an integration that assumes every DKG node exposes a production x402 paid-access endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.origintrail.io/concepts/knowledge-commerce.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.