Read enabled service authority metadata
const url = 'https://auth.example.invalid/service-endpoint-authority';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://auth.example.invalid/service-endpoint-authorityRequires service endpoints enabled; disabled route returns 404 before other guards. Origin is refused even for GET. This metadata grants no authority.
Responses
Section titled “Responses”Successful response.
object
object
Example
{ "v": 1, "kind": "service-endpoint-authority-info", "keys": [ { "kty": "OKP", "crv": "Ed25519" } ]}Headers
Section titled “Headers”JSON error. Route guards run before proof evaluation; parser failures are 400 and byte overflow is 413. An unexpected failure is 400 unless a route handles it separately.
object
Example
{ "outcome": "not-executed"}JSON error. Route guards run before proof evaluation; parser failures are 400 and byte overflow is 413. An unexpected failure is 400 unless a route handles it separately.
object
Example
{ "outcome": "not-executed"}JSON error. Route guards run before proof evaluation; parser failures are 400 and byte overflow is 413. An unexpected failure is 400 unless a route handles it separately.
object
Example
{ "outcome": "not-executed"}JSON error. Route guards run before proof evaluation; parser failures are 400 and byte overflow is 413. An unexpected failure is 400 unless a route handles it separately.
object
Example
{ "outcome": "not-executed"}Public admission cap (64 in flight), 10 second request deadline, or a route-specific unavailable read/effect. A service authority 503 may follow a binding; retain the request identity.
object
Example
{ "outcome": "not-executed"}