Alias for fetch for API route adapters that expect an api property.
Registered contract inputs.
Build a fully assembled request context from a framework-neutral request.
Build a fully assembled service context for schedules, outbox drains, commands, and background work.
Catch-all Web Fetch handler.
Final app ports after provider setup.
Build a Web Fetch handler for a route that cannot be a contract while still running the whole server pipeline — hooks, context creation, instrumentation, and framework error mapping. Request parsing is skipped and the body is left unconsumed for the handler. Raw routes are not added to the route registry; mount the returned handler yourself.
Register and build a single Web Fetch route handler imperatively.
Stop installed providers.
Beignet server adapted to the Web Fetch API.