Asset API Overview
Surface
The service uses minimal-API endpoint extensions. Native routes share the /asset prefix and asset OpenAPI tag. Compatibility routes retain the HR Operations shape and use asset-compat. Host health and service-information routes are registered in the composition root.
No route-based API version was found. Swagger/OpenAPI is registered. JWT middleware exists, but endpoint enforcement is absent. Tenant context and EF query filters scope data. Compatibility and gateway cutover make current maturity Transitional.
Classification
The API is Transitional. Capabilities explicitly described as absent are Not implemented. Host diagnostics and evidence routes are Foundation. Production exposure, ownership, and governance Require confirmation.
Source References
microservices/src/asset-service/Program.csmicroservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Api/AssetCompatEndpoints.cs