Developer Docs

Registry JSON Access

Narrative overview of how we expose registry payloads. This page keeps the human-readable context in the Developer stack, while the raw JSON remains in the Dev Tools area.

Where to grab the data

Use the dedicated Dev Tool at /dev/registry to copy the combined modules, apps, and ecosystems payload. It calls the /api/registry endpoint and exposes the response as a formatted JSON block with a copy helper.

Why split docs vs. tools?

  • Developer pages stay focused on explanations and onboarding.
  • Dev tools favor pragmatic JSON blocks, clipboard buttons, and raw data.
  • Linking the two keeps context close without mixing formats.

Workflow reminder

  1. Sync each package's registry.json via pnpm registry:register.
  2. Visit /dev/registry and copy the payload.
  3. Use that JSON for seed scripts, consoles, or parity checks.
FireUX logoFIReUX © 2026All rights reserved.