Web

Which stored-credential operations this build accepts

Receiver-capability descriptor. A client asks this before sending a selector, because a ToolPiper without the strict route answers 404 and the client must then refuse locally rather than downgrade to an unauthenticated raw request.

selectorContract is matched EXACTLY (role-operation-1); it is not a version to compare and there is no floor to raise. An unknown marker means unsupported, the same direction a 404 does.

Free on purpose: a 402 here would be indistinguishable from unsupported and would push a caller toward the downgrade this mode exists to ban. Advertisement is a routing agreement, never authority — the POST re-validates the whole shape independently.

get/v1/http/credential-operations

Request

  • Base URL: http://localhost:9998
  • URL: http://localhost:9998/v1/http/credential-operations
  • Auth: HTTP bearer

Response

The exact operation ids and selector contract this build accepts

selectorContract'role-operation-1' required

Exact marker. Any other value, including a later-looking one, means unsupported.

operationsstring[] required

Every operation id this build accepts, sorted. An id absent here is refused by the POST too.

Changes

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