Same models, same afternoon: 75% of first attempts got an answer, 93% within three. Publishing only one of those is misleading in one direction or the other.
Define the success you mean
Official SDKs often retry. A status figure that counts only first attempts describes an experience almost nobody has. A figure that counts eventual success after retries can hide how often users wait.
Publish both when you can, and document the retry policy next to the number. Align your application retries so an SDK, worker and queue do not multiply one user action into many paid attempts.