Routes

Route::exert() registers a normal Laravel route pointing to the controller's resolve() method:

Route::exert('/system', SystemController::class, ['GET', 'POST']);

The fluent form registers the same controller route:

Route::exert('/system')
    ->controller(SystemController::class, ['GET', 'POST']);

The method argument accepts a string, an array, or null. It is the third argument in the compact controller form and the second argument to controller() or action():

Value	Route behavior
'POST'	Accept POST requests.
['GET', 'POST']	Accept the listed methods, with Laravel's normal route behavior.
Omitted or null	Use Laravel's Route::any() methods.

Method names passed to the macro are case-insensitive. Each selected action still checks its own allowed methods.

Route an action directly

Use action() when an endpoint has one action and does not need controller selection:

Route::exert('/logout')
    ->action(LogoutAction::class, 'POST');

This route calls the action's initiate() method. It does not read the configured action key or use an action-controller registry, but it still checks route and action methods, runs action middleware, injects route parameters and container dependencies, supports Precognition, and converts the result to an HTTP response.

The class passed to action() must extend Exert\Action.

The returned route supports Laravel's usual names, middleware, prefixes, domains, and groups:

Route::prefix('internal')->middleware('auth')->group(function () {
    Route::exert('/system')
        ->controller(SystemController::class, ['GET', 'POST'])
        ->name('internal.system');
});

Import Route and your controller where you use these examples. Select a guard that matches your application, such as auth:sanctum when Sanctum is installed and configured.

You can also register the resolver yourself:

Route::match(['GET', 'POST'], '/system', [SystemController::class, 'resolve']);

Choose one registration for an endpoint. Both controller forms and direct action routes work with Laravel's route cache; they store class handlers rather than route closures.

Keep routes explicit

The generator does not modify route files. This makes a new action a deliberate addition: define the class, register it in the map, and make sure the endpoint accepts its method.

If two controllers share an action name such as create, their routes and controller-qualified metadata keep those operations distinct. A route name identifies the shared endpoint, not the individual action.

For action-specific logs, use request metadata. For the relationship between route and action methods, read HTTP methods.