Introducing Capability Map
It is the guardrails layer for n.codes.
It auto-maps what your app can do (APIs, schemas, components) and tells the LLM exactly what is
allowed to generate in a production setting.
Capability Map is the foundation of that, enabling agents to securely generate new features in
production, leveraging the capabilities of the existing backend and components.
Allowing users to generate their own custom features.
Entities
Data models surfaced as capabilities.
Actions
Mutations and commands the agent can use.
Queries
Approved data access patterns for answers.
Components
UI building blocks already in your app.
How is it different from MCP or API docs?
MCP
MCP is a protocol to access tools and resources. It does not define app-specific boundaries or
UI affordances.
API docs
API docs describe endpoints. They do not capture permissions, product constraints, or frontend
components. They are written for humans.
Capability map
Capability map merges APIs, schemas, UI components, constraints, and RBAC into a single
"allowed actions" set so users can generate features safely within guardrails.
Capability Map keeps agents inside the lines while unlocking user-generated features in
production.