Domain-Driven Design defines a Service as:
A SERVICE is an operation offered as an interface that stands alone in the model, without encapsulating state… [p. 105]
Yes, it’s a class with public methods, but in addition to that, it implements an interface that exposes those methods. At its core, the Service is the interface – the class that implements it is just an implementation detail.