Create a node lock for confidential compute
This endpoint attempts to find a suitable node and retrieve its public key for encryption through a two-step process:
- First, it tries to select an existing node with a public key directly.
- If no node is immediately available, it falls back to finding the cheapest compatible node and acquiring a new stack entry for it.
This endpoint is specifically designed for confidential compute scenarios where requests need to be encrypted before being processed by nodes.
Errors
- INTERNAL_SERVER_ERROR - Communication errors or missing node public keys
- SERVICE_UNAVAILABLE - No nodes available for confidential compute
Request body
Response
Node DH public key requested successfully
Changes
Changed in 5 of the 13 revisions of this API.125
- ○
added the new optional request property
new-optional-request-property
- ○
added the new optional request property
new-optional-request-property
- ○
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●
- ○
added the new optional request property
new-optional-request-property
- ○
added the new optional request property
new-optional-request-property
- ○
- ○
endpoint added
endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲