How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NEAR Protocol EXPERIMENTAL Light Client Proof API

The EXPERIMENTAL Light Client Proof API from NEAR Protocol — 1 operation(s) for experimental light client proof.

NEAR Protocol EXPERIMENTAL Light Client Proof API is one of 60 APIs that NEAR Protocol publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include EXPERIMENTAL Light Client Proof. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.

This API exposes 1 operation across 1 path, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 3.0.3.

Requests are made against 2 base URLs: https://api.fastnear.com, https://test.api.fastnear.com.

1 operations 1 paths 42 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.3
Base URL
https://rpc.mainnet.near.org
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

EXPERIMENTAL Light Client Proof 1
POST
/EXPERIMENTAL_light_client_proof
Returns the proofs for a transaction execution.
EXPERIMENTAL_light_client_proof body → 200

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are BlockHeaderInnerLiteView (9 properties), ExecutionOutcomeView (7 properties), JsonRpcRequest_for_EXPERIMENTAL_light_client_proof (4 properties), ExecutionOutcomeWithIdView (4 properties). Each schema is shown below with its type and property counts.

TxExecutionError
Error returned in the ExecutionOutcome in case of failure
ActionsValidationError
Describes the error for validating a list of actions.
JsonRpcResponse_for_RpcLightClientExecutionProofResponse_and_RpcLightClientProofError
object
2 properties 2 required
GlobalContractIdentifier
RpcLightClientExecutionProofRequest
object
1 property 1 required
InternalError
ActionErrorKind
RpcLightClientExecutionProofResponse
object
4 properties 4 required
ExecutionMetadataView
object
3 properties 1 required
DepositCostFailureReason
string
Reason why a gas key transaction failed at the deposit/account level. In these cases, gas is still charged from the gas key.
CompilationError
MethodResolveError
string
PublicKey
string
CostGasUsed
object
Shows gas profile. More info [here](https://near.github.io/nearcore/architecture/gas/gasprofile.html?highlight=WASMHOSTCOSTexample-transaction-gas-profile).
3 properties 3 required
NearGas
integer
NearToken
string
WasmTrap
A kind of a trap happened during execution of a binary
ExecutionOutcomeView
object
7 properties 6 required
RpcRequestValidationErrorKind
AccountId
string
NEAR Account Identifier. This is a unique, syntactically valid, human-readable account identifier on the NEAR network. [See the crate-level docs for informatio…
StorageError
Errors which may occur during working with trie storages, storing trie values (trie nodes and state values) by their hashes.
JsonRpcRequest_for_EXPERIMENTAL_light_client_proof
object
4 properties 4 required
RpcLightClientProofError
PrepareError
Error that can occur while preparing or executing Wasm smart-contract.
InvalidTxError
An error happened during TX execution
Direction
string
LightClientBlockLiteView
object
3 properties 3 required
MissingTrieValueContext
Contexts in which StorageError::MissingTrieValue error might occur.
CryptoHash
string
BlockHeaderInnerLiteView
object
A part of a state for the current head of a light client. More info [here](https://nomicon.io/ChainSpec/LightClient).
9 properties 9 required
ReceiptValidationError
Describes the error for validating a receipt.
ActionError
object
An error happened during Action execution
2 properties 1 required
ExecutionOutcomeWithIdView
object
4 properties 4 required
FunctionCallError
Serializable version of near-vm-runner::FunctionCallError. Must never reorder/remove elements, can only add new variants at the end (but do that very carefully…
ShardId
integer
The shard identifier. It may be an arbitrary number - it does not need to be a number in the range 0..NUMSHARDS. The shard ids do not need to be sequential or…
InvalidAccessKeyError
AccountContractView
RPC view of a non-empty [AccountContract]. The AccountContract::None variant is represented externally as a JSON null via Option, so this enum only carries the…
MissingTrieValue
object
2 properties 2 required
MerklePathItem
object
2 properties 2 required
ErrorWrapper_for_RpcLightClientProofError
HostError
ExecutionStatusView

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-experimental-light-client-proof-api-openapi.yml Raw ↑

Other APIs NEAR Protocol publishes across the network.

NEAR Protocol accounts API
NEAR Protocol Block API
NEAR Protocol Block Effects API
NEAR Protocol Broadcast Tx Async API
NEAR Protocol Broadcast Tx Commit API
NEAR Protocol Changes API
NEAR Protocol Chunk API
NEAR Protocol Client Config API
NEAR Protocol EXPERIMENTAL Call Function API
NEAR Protocol EXPERIMENTAL Changes API
NEAR Protocol EXPERIMENTAL Changes In Block API
NEAR Protocol EXPERIMENTAL Congestion Level API
Where this information came from

This is an independent, third-party profile of NEAR Protocol EXPERIMENTAL Light Client Proof API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.