Bootstrapping the Evolution CMS API Inside a Standalone AJAX PHP File

Sometimes an Evolution CMS project ends up with a standalone PHP endpoint that still needs access to CMS data, settings, or parsing helpers. The safe way to do that is to bootstrap the API deliberately instead of copying random include lines until something starts working.

The original pattern defined MODX_API_MODE, loaded config.inc.php, started the CMS session, included the document parser, and then initialized DocumentParser. That is the right general shape for standalone AJAX handlers that still need Evolution context.

The practical rule is simple: if an external PHP file needs CMS data, initialize the CMS properly. Otherwise you end up with half-working code that breaks as soon as sessions, settings, or parser behavior matter.