WCNWeb3 Capital Network

DEVELOPERS

Developer docs start with the public API boundary.

WCN is not publishing a public API claim before the boundary is ready. This page gives developers the current build surface: public docs, proof workflow concepts, and the waitlist path.

Read system docsJoin developer interest

Public API boundary

Developer docs coming with public API boundary.

Do not assume a live public API, SDK, sandbox, or GitHub repository from this page. The current public surface is documentation and proof-workflow readiness.

  • Do not imply a live API
  • Do not publish unconfirmed GitHub/SDK links
  • Do not expose private proof data through public interfaces

Current developer surface

API status
Public API boundary pendingMust not be marketed as an open API.
Available now
Wiki, System Atlas, Proof Ledger boundary, System Library
Agent execution
Described as a mechanism; public integration surface is unconfirmed
GitHub / SDK
Publish only after real URLs are confirmed

Proof workflow mental model

  1. 01
    Declare participation scope
  2. 02
    Submit reviewable evidence
  3. 03
    Pass review and risk screening
  4. 04
    Publish only anonymized summaries
  5. 05
    Keep revocation and dispute boundaries

Where to start

Use the public pages to understand the workflow before asking for private integration material.

01

Understand the loop

Node → Deal → Task → Proof → Decision is the minimum developer path for understanding WCN.

See mechanism
02

Understand public fields

Developers need to know what can be public and what must never appear in public interfaces.

View Proof Ledger
03

Read the system library

The source system docs define the knowledge boundary for future APIs and agent workflows.

Open systems
04

Join developer interest

Describe what you want to build, what boundary you need, and whether private data is involved.

Open contact routing