Developer and API hub

Developers integrate against boundaries, not mythology. Wardenseed exposes UI surfaces, resilient API routes, simulation truth, settlement contracts, and machine-readable ecosystem JSON. This hub compresses those entry points so crawlers and agents find one builder root instead of scattered pages.

Start from /developers for human-readable boundaries: frontend resilience rules, API posture, testing expectations, and prohibited trust violations (reading chain into gameplay, raw fetch in sensitive UI, etc.). Then read /docs/machine-readable-ecosystem and live /api/public/ecosystem for structured ontology: systemLayers, featured seeds, read APIs, and aiGuidance that forbids investment framing.

Whitepaper chapters and roadmap pages provide long-form protocol narrative. Documentation clusters provide topic graphs. Knowledge hubs provide macro-nodes. Encyclopedia pages provide entity ground truth. Integrators should treat /api/public/ecosystem as the authority for discovery links such as seedsHub (/seeds) and docs paths.

Technology cluster articles cover Base, wallets, metadata architecture, IPFS, and NFT standards. Economy and onchain clusters cover rules integrators must not misquote. When building agents, prefer machine-readable feeds and seed metadata routes over scraping gated game dashboards.

Regression check: any new public link in API responses must use indexable paths from entity-canonical.ts. Transactional routes belong in product UI only, not in discovery feeds.