Endpoint mapping contract
Pulse Routing
Pulse routing defines how source files map to same-origin /api routes and how those routes are exposed to runtime callers, embeds, and automation surfaces.
Route contract reference for mapping Pulse files to API endpoints.
Implementation focus
Use this page when creating or refactoring server routes so call paths and deployment behavior remain predictable.
Expected outcomes
- Map source layout to stable /api route contracts.
- Avoid route collisions during iterative releases.
- Preserve clear ownership across handler files and surfaces.