Documentation

Refunds When execution of a receipt fails or there is some unused amount of prepaid gas left after a function call, the Runtime generates refund receipts. The are 2 types of refunds: • Refunds for the

Registers API Registers allow the host function to return the data into a buffer located inside the host oppose to the buffer located on the client. A special operation can be used to copy the content

Routing table exchange algorithm Every node on the network stores its own copy of the Routing Graph . nearcore exchanges this graph in two steps. When a connection is set up, the two nodes do a full s

Runtime Runtime layer is used to execute smart contracts and other actions created by the users and preserve the state between the executions. It can be described from three different angles: going st

Runtime crate Runtime crate encapsulates the logic of how transactions and receipts should be handled. If it encounters a smart contract call within a transaction or a receipt it calls near-vm-runner,

Overview This chapter covers the NEAR Protocol runtime specification. Runtime Specification • Account Receipt Storage • Actions • Applying chunk • Components • Runtime Crate • Bindings Specification •

RuntimeConfig The structure that holds the parameters of the runtime, mostly economics. storagecostbyteperblock type: Balance The cost to store one byte of storage per block. storagecostbyteperblock t

RuntimeFeesConfig Economic parameters for runtime actionreceiptcreationconfig type: Fee Describes the cost of creating an action receipt, ActionReceipt, excluding the actual cost of actions. datarecei

Selecting Chunk and Block Producers Background Near is intended to be a sharded blockchain. At the time of writing (March 2021), challenges (an important security feature for a sharded network) are no

StateRecord type: Enum Enum that describes one of the records in the state storage. Account type: Unnamed struct Record that contains account information for a given account ID. accountid type: Accoun

StorageUsageConfig Describes cost of storage per block accountcost type: Gas Base storage usage for an account datarecordcost type: Gas Base cost for a k/v record keycostperbyte type: Gas Cost per byt

Transaction See Transactions documentation in the Runtime Specification section.

Transactions A transaction in Near is a list of actions and additional information. There are two versions of a transaction: ![allow(unused)] fn main() { pub enum Transaction { V0(TransactionV0), V1(T

Transactions in the Blockchain Layer A client creates a transaction, computes the transaction hash and signs this hash to get a signed transaction. Now this signed transaction can be sent to a node. W

Trie API Here we provide a specification of trie API. After this NEP is merged, the cases where our current implementation does not follow the specification are considered to be bugs that need to be f

Upgradability This part of specification describes specifics of upgrading the protocol, and touches on few different parts of the system. Three different levels of upgradability are: • Updating withou

VMConfig Config of wasm operations. extcosts type: [ExtCostsConfig] ExtCostsConfig Costs for runtime externals growmemcost type: u32 Gas cost of a growing memory by single page. regularopcost type: u3

/api-reference/openapi.json post /v1/users/me/invitations/{invitationid}/accept Accepts a pending invitation and adds the user as a member of the organization.

/api-reference/openapi.json post /v1/invitations/{token}/accept Accepts an invitation using its token. The authenticated user's email must match the invitation email.

/api-reference/openapi.json post /v1/organizations/{orgid}/members Adds a new member to the organization. The authenticated user must be an owner or admin.

Configure Aider and Zed to use NEAR AI Cloud as an OpenAI-compatible provider. NEAR AI Cloud exposes an OpenAI-compatible API, so Aider and Zed can use NEAR AI models with a base URL, an API key, and

OpenAI-compatible REST API for private, verifiable AI inference on NEAR AI Cloud The NEAR AI Cloud API is a REST API served from a single base URL. Its documented OpenAI-compatible inference surfaces

/api-reference/openapi.json post /v1/audio/transcriptions Transcribe audio files using Whisper models. Accepts audio file uploads via multipart/form-data. Supports MP3, WAV, WEBM, FLAC, OGG, and M4A f

Explore NEAR AI Cloud model catalog NEAR AI Cloud provides access to leading AI models, each optimized for different use cases ranging from advanced reasoning and tool calling to long-context processi

/api-reference/openapi.json patch /v1/admin/models Upserts (inserts or updates) pricing and metadata for one or more models. Only authenticated admins can perform this operation. The body should be an

/api-reference/openapi.json delete /v1/admin/models/pricing-changes/{id}

/api-reference/openapi.json delete /v1/organizations/{orgid}/members/invitations/{invitationid} Cancels a pending invitation for the organization. Only owners and admins can cancel invitations.

/api-reference/openapi.json delete /v1/organizations/{orgid}/invitations/{invitationid} Cancels a pending invitation for the organization. Only owners and admins can cancel invitations. This endpoint

/api-reference/openapi.json post /v1/checkapikey Validates the provided API key (via Bearer token), checks rate limits, and verifies the organization has sufficient credits. This endpoint is designed

Configure Cline, Roo Code, and Kilo Code with NEAR AI Cloud's OpenAI-compatible API. Cline, Roo Code, and Kilo Code can use NEAR AI Cloud through OpenAI-compatible provider settings. They share the sa