Authentication
A request carries a provider-issued bearer token:
Authorization: Bearer <token>A provider may document an equivalent scheme, but it must use the 401 and
403 contract in the submission response table so that
a client can distinguish “not authenticated” from “not allowed to send this”.
Credential issuance, scoping, and rotation are deployment concerns.
An Idempotency-Key is scoped to the authenticated principal. Authentication
therefore happens before the provider reserves or looks up the key, preventing
one principal from colliding with or replaying another principal’s response.
