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 Congestion Level API

The EXPERIMENTAL Congestion Level API from NEAR Protocol — 1 operation(s) for experimental congestion level.

NEAR Protocol EXPERIMENTAL Congestion Level 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 Congestion Level. 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 12 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 12 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 Congestion Level 1
POST
/EXPERIMENTAL_congestion_level
EXPERIMENTAL congestion level
EXPERIMENTAL_congestion_level body → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are JsonRpcRequest_for_EXPERIMENTAL_congestion_level (4 properties), JsonRpcResponse_for_RpcCongestionLevelResponse_and_RpcChunkError (2 properties), RpcCongestionLevelResponse (1 property). Each schema is shown below with its type and property counts.

ChunkHash
InternalError
JsonRpcResponse_for_RpcCongestionLevelResponse_and_RpcChunkError
object
2 properties 2 required
RpcCongestionLevelResponse
object
1 property 1 required
ErrorWrapper_for_RpcChunkError
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…
BlockId
RpcChunkError
CryptoHash
string
RpcRequestValidationErrorKind
JsonRpcRequest_for_EXPERIMENTAL_congestion_level
object
4 properties 4 required
RpcCongestionLevelRequest
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

near-experimental-congestion-level-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 Genesis Config API
Where this information came from

This is an independent, third-party profile of NEAR Protocol EXPERIMENTAL Congestion Level 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.