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

post/v1/nodes/lock

Base URL
https://api.atoma.network
Auth
HTTP bearer
TypeScript
https://skmtc.dev/atomaai/apis/atoma-proxy/docs/v1/nodes/lock/post.ts
A function with typed inputs. Its response is checked against the schema.

max_num_tokensinteger nullable

The number of tokens to be processed for confidential compute (including input and output tokens)

modelstring required

The model to lock a node for

timeoutinteger nullable

An optional timeout period for the locked compute units, in seconds

Node DH public key requested successfully

node_small_idinteger required

The node small id for the selected node

public_keystring required

The public key for the selected node, base64 encoded

stack_entry_digeststring nullable

Transaction digest for the transaction that acquires the stack entry, if any

stack_small_idinteger required

The stack small id to which an available stack entry was acquired, for the selected node

May 12, 2025f0bf5a2dde0f Revision changes
- info
  added the new optional request property
- info
  added the new optional request property
Apr 11, 2025e19be1e82c3b Revision changes
- warning
  removed the request property
- warning
  removed the request property