# Developer reference and release inventory

Explore the exact 7.3.4 endpoint, setting, CLI, and configuration inventory.

The committed release inventory is generated by the plugin source and preserved byte for byte.

## Release artifacts

*   [7.3.4 public manifest](https://cybermaps.dev/product/manifest.json)
*   [7.3.4 configuration JSON Schema](https://cybermaps.dev/specs/ai-configuration/7.3.4/schema.json)
*   [7.3.4 configuration field catalog](https://cybermaps.dev/specs/ai-configuration/7.3.4/catalog.json)
*   [Full technical source guide](https://cybermaps.dev/product/documentation.md)

## Configuration roots

General settings live in `cybermaps_settings`. Discovery strategy, crawler policy, and identity have separately owned options and sanitizers. Read them through the plugin configuration store; preserve unrelated settings on partial saves.

## Build an extension

Use the [extension and lifecycle reference](https://cybermaps.dev/docs/extension-api/). An extension owns its namespace, settings, lifecycle, and release artifact. It must not replace Core or depend on its internal service container.

## Site agent API

This website’s [public read-only API](https://cybermaps.dev/docs/site-api/) reads these published pages. It is separate from the WordPress plugin’s optional authenticated MCP interface.