Nodes
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 keysSERVICE_UNAVAILABLE
- No nodes available for confidential compute
POST
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Body
application/json
The model to lock a node for
Request body for creating a node lock
Response
200
application/json
Node DH public key requested successfully
The response body for selecting a node's public key for encryption from a client. The client will use the provided public key to encrypt the request and send it back to the proxy. The proxy will then route this request to the selected node.