Discovery

Protected-resource metadata (RFC 9728)

What gates this resource, at the fixed path a client constructs without being told. authorization_servers is absent rather than empty: there is no OAuth issuer here, the field is optional, and naming one that does not exist would be a false claim in machine form. Carries an agent_auth block and the x402 particulars. Every 402 from this store points here in its WWW-Authenticate header.

get/.well-known/oauth-protected-resource

Request

  • Base URL: https://scvd.store
  • URL: https://scvd.store/.well-known/oauth-protected-resource
  • Auth: none required

Headers

If-None-Matchstring

Send a prior ETag (SHA-256 of exact response bytes). Unchanged content returns 304 with no body.

Response

OK

resourcestring uri required
resource_namestring
resource_documentationstring uri required
resource_policy_uristring uri
resource_tos_uristring uri
bearer_methods_supportedstring[] required

Empty, and that is the answer: this store issues no bearer tokens, so it supports no way of presenting one. authorization_servers is absent entirely for the same reason — there is no OAuth issuer, the field is optional, and naming one that does not exist would be a false claim in machine form.

scopes_supportedstring[]

Changes

No recorded changes to this operation across all 1 revision of this API.