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 Protocol Config API

The EXPERIMENTAL Protocol Config API from NEAR Protocol — 1 operation(s) for experimental protocol config.

NEAR Protocol EXPERIMENTAL Protocol Config 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 Protocol Config. 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 37 schemas. It is described by OpenAPI 3.2.0, at version 1.2.11.

Requests are made against the base URL https://rpc.mainnet.near.org.

1 operations 1 paths 37 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.11
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 Protocol Config 1
POST
/EXPERIMENTAL_protocol_config
EXPERIMENTAL protocol config
EXPERIMENTAL_protocol_config body → 200

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are ExtCostsConfigView (90 properties), LimitConfig (39 properties), RpcProtocolConfigResponse (31 properties), VMConfigView (21 properties). Each schema is shown below with its type and property counts.

ActionCreationConfigView
object
Describes the cost of creating a specific action, Action. Includes all variants.
11 properties
DataReceiptCreationConfigView
object
The fees settings for a data receipt creation
2 properties
AccountIdValidityRulesVersion
integer
ExtCostsConfigView
object
Typed view of ExtCostsConfig to preserve JSON output field names in protocol config RPC output.
90 properties
JsonRpcRequest_for_EXPERIMENTAL_protocol_config
object
4 properties 4 required
NearToken
string
RpcProtocolConfigError
ShardLayout
A versioned struct that contains all information needed to assign accounts to shards. Because of re-sharding, the chain may use different shard layout to split…
Finality
string
Different types of finality.
RpcRequestValidationErrorKind
AccessKeyCreationConfigView
object
Describes the cost of creating an access key.
3 properties 3 required
AccountCreationConfigView
object
The structure describes configuration for creation of new accounts.
2 properties
InternalError
RpcProtocolConfigResponse
object
31 properties
JsonRpcResponse_for_RpcProtocolConfigResponse_and_RpcProtocolConfigError
object
2 properties 2 required
WitnessConfigView
object
Configuration specific to ChunkStateWitness.
3 properties
CongestionControlConfigView
object
The configuration for congestion control. More info about congestion [here](https://near.github.io/nearcore/architecture/how/receipt-congestion.html?highlight=…
12 properties
NearGas
integer
StorageGetMode
string
This enum represents if a storageget call will be performed through flat storage or trie
SyncCheckpoint
string
CryptoHash
string
VMConfigView
object
21 properties
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…
StorageUsageConfigView
object
Describes cost of storage per block
2 properties
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…
Fee
object
Costs associated with an object that can only be sent over the network (and executed by the receiver). NOTE: sendsir or sendnotsir fees are usually burned when…
3 properties 3 required
ShardLayoutV3
object
Counterpart to ShardLayoutV3 composed of maps with string keys to aid serde serialization.
5 properties 5 required
BlockId
RpcProtocolConfigRequest
object
ShardLayoutV2
object
Counterpart to ShardLayoutV2 composed of maps with string keys to aid serde serialization.
7 properties 5 required
LimitConfig
object
Describes limits for VM and Runtime. TODO 4139: consider switching to strongly-typed wrappers instead of raw quantities
39 properties
ShardLayoutV1
object
4 properties 2 required
RuntimeConfigView
object
View that preserves JSON format of the runtime config.
6 properties
VMKind
ShardLayoutV0
object
A shard layout that maps accounts evenly across all shards -- by calculate the hash of account id and mod number of shards. This is added to capture the old ac…
2 properties 2 required
ErrorWrapper_for_RpcProtocolConfigError
RuntimeFeesConfigView
object
Describes different fees for the runtime
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-experimental-protocol-config-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 Protocol Config 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.