Avalanche AVAX MCP
REMOTE · BUILD.AVAX.NETWORK · SCANNED AUG 3
Search and retrieve Avalanche blockchain documentation for building on AVAX.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 48 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4919 tokens (~89/item across 55 items; 48 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability check failed: schema churn in the 8 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · build.avax.network
claude mcp add --transport http airpote-avalanche-docs https://build.avax.network/api/mcp
[mcp_servers.airpote-avalanche-docs] url = "https://build.avax.network/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"airpote-avalanche-docs": {
"type": "remote",
"url": "https://build.avax.network/api/mcp",
"enabled": true
}
}
} openclaw mcp add airpote-avalanche-docs --url https://build.avax.network/api/mcp --transport streamable-http
mcp_servers:
airpote-avalanche-docs:
url: "https://build.avax.network/api/mcp" {
"mcpServers": {
"airpote-avalanche-docs": {
"type": "http",
"url": "https://build.avax.network/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.
- 29 Jul 26 −1
- Stability: 0.07 → fail ▼ security
- Tool “github_get_file” was removed ▼ security
- Tool “github_list_repositories” was removed ▼ security
- Tool “github_search_code” was removed ▼ security
- Tool “blockchain_get_contract_info” rewrote its description, which is the text the model reads security
- Tool “blockchain_get_native_balance” rewrote its description, which is the text the model reads security
- Tool “blockchain_lookup_address” rewrote its description, which is the text the model reads security
- Tool “platform_get_blockchains” rewrote its description, which is the text the model reads security
- Tool “platform_get_current_validators” rewrote its description, which is the text the model reads security
- Tool “platform_get_pending_validators” rewrote its description, which is the text the model reads security
- Schema quality: 56 → 89 ▼ functional
- Schema quality: excellent → good functional
- Server version: 2.1.0 → 2.4.0 functional
- New tool “build_plan” functional
- New tool “chain_stats” functional
- New tool “console_flow” functional
- New tool “console_link” functional
- New tool “onchain_activity” functional
- New tool “onchain_lookup” functional
- New tool “onchain_query” functional
- “platform_get_blockchains” added an optional parameter “limit” cosmetic
- “platform_get_blockchains” added an optional parameter “offset” cosmetic
- “platform_get_current_validators” added an optional parameter “limit” cosmetic
- “platform_get_current_validators” added an optional parameter “offset” cosmetic
- “platform_get_pending_validators” added an optional parameter “limit” cosmetic
- “platform_get_pending_validators” added an optional parameter “offset” cosmetic
- “platform_get_subnets” added an optional parameter “limit” cosmetic
- “platform_get_subnets” added an optional parameter “offset” cosmetic
- “blockchain_get_contract_info” reworded the description of “address” cosmetic
- “blockchain_get_contract_info” reworded the description of “chainId” cosmetic
- “blockchain_get_native_balance” reworded the description of “chainId” cosmetic
- “blockchain_lookup_address” reworded the description of “address” cosmetic
- “blockchain_lookup_address” reworded the description of “chainId” cosmetic
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://build.avax.network/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=avax.network | CN=YE1,O=Let's Encrypt,C=US | 2 Jul 2026 | 30 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 5a9732dca83390f0c1a711a1d02499c0553 |
| SANs: *.avax.network, *.cchain.explorer.avax.network, avax.network, cchain.explorer.avax.network | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of build.avax.network. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| avax.network. | present | 2371 | 13 | Verified |
| build.avax.network. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=0 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://build.avax.network/api/mcp | Verified | 200 | |
| http (plaintext) | http://build.avax.network/api/mcp | HTTPS enforced | 301 | https://build.avax.network/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
acp_list ~107
List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of ACPs to return (default: 50) |
| status | string | — | Filter by ACP status (case-insensitive) |
| track | string | — | Filter by ACP track. Matches Standards, Best Practices, Meta, or Subnet. |
No output schema declared.
No examples provided.
acp_lookup ~93
Look up Avalanche Community Proposals (ACPs) by number, title, or topic. When a number is provided the structured ACP record is returned (title, status, track, authors, cross-references).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of results (default: 8) |
| number | number | — | ACP number, if known |
| query | string | — | ACP title, topic, or keyword |
No output schema declared.
No examples provided.
avalanche_docs_fetch ~44
Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page URL path (e.g., /docs/primary-network/overview) |
No output schema declared.
No examples provided.
avalanche_docs_list_sections ~25
Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
avalanche_docs_search ~62
Compatibility alias for docs_search. Prefer docs_search for new clients.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of chunk results (default: 10) |
| query | string | yes | The search query |
| source | string | — | Filter by documentation source (optional) |
No output schema declared.
No examples provided.
blockchain_get_contract_info ~62
Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address (0x...) |
| chainId | string | — | 43114 for C-Chain mainnet, 43113 for Fuji |
No output schema declared.
No examples provided.
blockchain_get_native_balance ~63
Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address (0x...) |
| chainId | string | — | 43114 for C-Chain mainnet, 43113 for Fuji |
No output schema declared.
No examples provided.
blockchain_lookup_address ~62
Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address (0x...) |
| chainId | string | — | 43114 for C-Chain mainnet, 43113 for Fuji |
No output schema declared.
No examples provided.
blockchain_lookup_chain ~43
Look up a blockchain by its ID — name, VM type, and subnet.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | yes | The blockchain ID |
| network | string | — | — |
No output schema declared.
No examples provided.
blockchain_lookup_subnet ~48
Look up a Subnet / L1 by its ID — validators, chains, and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | — |
| subnetId | string | yes | The Subnet ID |
No output schema declared.
No examples provided.
blockchain_lookup_transaction ~87
Look up a transaction by hash on Avalanche (C-Chain, P-Chain, or X-Chain). Supports 0x format (C-Chain) and CB58 format (P/X-Chain).
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Network to search |
| txHash | string | yes | Transaction hash (0x... for C-Chain, CB58 for P/X-Chain) |
No output schema declared.
No examples provided.
blockchain_lookup_validator ~64
Look up a validator by node ID — stake, uptime, delegation info.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | — |
| nodeId | string | yes | Node ID (e.g. NodeID-...) |
| subnetId | string | — | Subnet ID (default: Primary Network) |
No output schema declared.
No examples provided.
build_plan ~434
Generate a step-by-step, copy-pasteable runbook for an Avalanche operation — Builder Console (no-code) path plus the equivalent platform-cli / SDK / interchain-kit commands. Read-only: never signs. operation: create-l1 (launch an L1); use ictt or interchain-kit for any CROSS-CHAIN / interoperability work — bridging tokens, sending cross-chain (ICM / Teleporter / Warp) messages, or connecting your L1 to C-Chain or other L1s (interchain-kit also lets you iterate locally first); validator-manager; staking; transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | — | transfer: amount |
| chainId | string | — | create-l1: EVM chain ID |
| duration | string | — | staking: staking period (e.g. 336h) |
| example | string | — | interchain-kit: which example to run |
| homeChain | string | — | ictt: home chain (where the token originates) |
| name | string | — | create-l1: L1 name (default: myL1) |
| network | string | — | Target network (default: fuji) |
| nodeId | string | — | staking: NodeID-… |
| operation | string | yes | Which runbook to generate |
| remoteChain | string | — | ictt: destination chain (required for operation=ictt) |
| stake | string | — | staking: stake amount |
| to | string | — | transfer: destination address (transferKind=send) |
| token | string | — | ictt: token contract address (or "native") |
| tokenSymbol | string | — | create-l1: native token symbol |
| tokenType | string | — | ictt: token type (default: erc20) |
| transferKind | string | — | transfer: kind (default: send) |
| type | string | — | validator-manager: manager type (alias of validatorManager) |
| validatorManager | string | — | create-l1 / validator-manager: model (default: poa) |
| vm | string | — | create-l1: VM type (default: subnet-evm) |
No output schema declared.
No examples provided.
chain_stats ~340
On-chain statistics via the query gateway, which picks the most accurate live source PER FIELD and stamps it (sources/warnings in the response). target=chain: tx count/gas/fees/active senders/avg gas price over a recent window (window=recent, `hours`, max 720h = 30 days) OR a time-series (window=series, `days`, max 365). target=contract: per-contract tx/sender/gas totals (`days`, max 365 — use this for contract activity beyond 30 days). target=network: current P-chain validator snapshot. IMPORTANT: relay any `warnings` notes to the user verbatim-in-substance (e.g. gas coverage windows or accuracy caveats) — never present a flagged value as exact. Note: C-Chain gasUsed is gas-target-regulated, so daily gas is ~stable even as tx count varies — expected, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | — | EVM chain ID (default: C-Chain for the network) |
| days | number | — | Look-back days for series / contract (default: 30, max 365) |
| hours | number | — | Look-back hours for window=recent (default: 24, max 720) |
| network | string | — | Network (default: mainnet) |
| target | string | — | chain (default) | contract | network |
| timeInterval | string | — | Bucket size for window=series (default: day) |
| value | string | — | Contract address (target=contract) |
| window | string | — | chain: recent aggregate (default) or series |
No output schema declared.
No examples provided.
cli_lookup_command ~81
Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs.
| Name | Type | Req | Description |
|---|---|---|---|
| cli | string | — | CLI surface to search. Defaults to all. |
| limit | number | — | Maximum number of results (default: 8) |
| query | string | yes | Command, flag, or task to look up |
No output schema declared.
No examples provided.
console_flow ~105
Builder Console flow knowledge. Call with NO `flow` to list every flow (summaries + deep-links); call with a `flow` key to explain it (ordered steps, equivalent CLI, whether it signs transactions, deep-link). Flows: create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, staking, transfers, interchain-kit-local.
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | — | Flow key to explain. Omit to list all flows. |
No output schema declared.
No examples provided.
console_link ~111
Return a deep-link into a specific Builder Console flow (create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, staking, transfers, interchain-kit-local). For faucet on mainnet, returns a note that there is no mainnet faucet.
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | The console flow to link to |
| network | string | — | Network (only affects faucet; default: fuji) |
| validatorManager | string | — | Validator-manager variant (default: poa) |
No output schema declared.
No examples provided.
docs_fetch ~38
Fetch a specific documentation page as markdown
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page URL path (e.g., /docs/primary-network/overview) |
No output schema declared.
No examples provided.
docs_list_sections ~18
List available documentation sections and their page counts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
docs_search ~72
Search body-level chunks across Avalanche documentation, academy courses, integrations, and blog posts. Returns source citations and matching excerpts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of chunk results (default: 10) |
| query | string | yes | The search query |
| source | string | — | Filter by documentation source (optional) |
No output schema declared.
No examples provided.
info_acps ~44
Get information about Avalanche Community Proposals (ACPs), including their status and vote counts.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_get_blockchain_id ~82
Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The blockchain alias (e.g., "X", "P", "C", or a full blockchain name) |
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_get_network_id ~41
Get the numeric ID of the Avalanche network this node is participating in.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_get_network_name ~42
Get the human-readable name of the Avalanche network this node is participating in.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_get_node_version ~47
Get the version of the node, including the database version, git commit, and API compatibility info.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_get_tx_fee ~46
Get the current transaction fees for the network, returned in both nAVAX and AVAX.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_is_bootstrapped ~68
Check whether a given chain has finished bootstrapping on the node.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | The chain ID or alias to check (e.g., "X", "P", "C") |
| network | string | — | The Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
info_peers ~80
Get a list of peers this node is connected to. Optionally filter by specific NodeIDs.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | The Avalanche network to query (default: mainnet) |
| nodeIDs | array | — | Optional list of NodeIDs to filter peers by (e.g., ["NodeID-AbC..."]). If omitted, all peers are returned. |
No output schema declared.
No examples provided.
onchain_activity ~295
Time-windowed on-chain activity. scope=chain/address returns the transaction COUNT over the last `hours` (max 720h = 30 days; for longer windows use chain_stats series or onchain_query day-based ops) plus a recent sample. For a token/contract use scope=token (transfers). scope=primary covers P/X-chain and DEFAULTS to P-Chain when no blockchainId is given (so "last N P-chain transactions" just works). A value with no scope defaults to address.
| Name | Type | Req | Description |
|---|---|---|---|
| blockchainId | string | — | Blockchain ID for scope=primary (default: P-Chain) |
| chainId | string | — | EVM chain ID (default: C-Chain for the network) |
| feed | string | — | transactions (default) | transfers | erc20Transfers | nftTransfers |
| fromTimestamp | number | — | Unix start time (scope=primary) |
| hours | number | — | Look-back window in hours for EVM transaction feeds (default: 2 for chain, max 720) |
| network | string | — | Network (default: mainnet) |
| pageSize | number | — | Max rows (default: 25) |
| scope | string | yes | address | chain | token | contract | primary |
| toTimestamp | number | — | Unix end time (scope=primary) |
| value | string | — | Address/contract/token (omit for scope=chain) |
No output schema declared.
No examples provided.
onchain_lookup ~277
PRIMARY lookup tool — use this (not raw RPC) to resolve/describe any on-chain identifier in one call: an EVM address (native + token balances, recent txs, contract metadata + isContract), a contract/token (metadata + deployment + recent transfers), an NFT (collection + tokenId), a tx hash, a subnet ID, a NodeID validator, a P-/X-Chain account (P-…/X-… → P-Chain balance), or a chain name/id. Use this for any address balance / contract-info / token / identity question. `kind` auto-detects; network is inferred from P-/X-Chain prefixes. Backed by Glacier + P-Chain RPC.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | string | — | EVM chain ID for EVM kinds (default: C-Chain for the network) |
| include | array | — | Extra data for an address (e.g. ["nfts"]) |
| kind | string | — | Entity kind (default: auto-detect from value) |
| network | string | — | Network (default: mainnet) |
| tokenId | string | — | NFT token ID (kind=nft) |
| value | string | yes | The identifier: 0x address / 0x tx hash / NodeID-… / subnetId / chain name or id |
No output schema declared.
No examples provided.
onchain_query ~550
PRIMARY tool for indexed on-chain stats/activity/totals — prefer this over raw RPC for chain data. Each `op` is a backend-agnostic intent: the query gateway selects the most accurate live source per field (indexed DB / pre-aggregated metrics / Data API), stamps every field (`sources`), and flags any caveat (`warnings`) — relay warnings to the user, never present a flagged value as exact. Pick an `op` and pass its `params`; `chainId` is an allowlisted EVM chain (43114 C-Chain, 43113 Fuji, + L1s). Lookback: hour-based ops (chainStatsRecent/chainActivity/addressActivity) max 720h (30 days); day-based ops (chainStatsSeries/contractStats/chainGasTotal/protocolRanking/contractGasFlow/topUnknownContracts) max 365 days — use a day-based op for windows over 30 days. Ops: chainStatsRecent {chainId, hours≤720} — tx count/gas/fees/active senders/avg gas price over the last N hours; chainStatsSeries {chainId, days≤365, bucket: hour|day|week|month} — bucketed time-series of the same; addressActivity {chainId, address, hours≤720, limit≤100} — tx count + recent sample for an address in a window; chainActivity {chainId, hours≤720, limit≤100} — tx count + recent sample chain-wide in a window; contractStats {chainId, contract, days≤365} — tx/unique-sender/gas totals for a contract; protocolRanking {chainId, contracts[≤25], days≤365, orderBy: txCount|gasUsed|uniqueSenders|feesPaidAvax, dir: asc|desc, limit≤100} — rank a set of contracts; contractGasFlow {chainId, contract, days≤365, limit≤100} — gas received/given per counterparty; topUnknownContracts {chainId, exclude[≤25], days≤365, limit≤100} — top contracts by gas excluding a set; chainGasTotal {chainId, days≤365} OR {chainId, fromDate, toDate} — total tx/gas/fees over N days or a YYYY-MM-DD range (≤365d). Note: C-Chain gasUsed is gas-target-regulated → ~stable day-to-day even as txCount varies (expected, not a bug).
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | yes | The query operation |
| params | object | yes | Op-specific parameters (see description); validated server-side. |
No output schema declared.
No examples provided.
platform_get_balance ~63
Get the AVAX balance of one or more P-Chain addresses
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | List of P-Chain addresses to query (e.g. P-avax1...) |
| network | string | — | Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
platform_get_block ~67
Get a P-Chain block by its block ID
| Name | Type | Req | Description |
|---|---|---|---|
| blockID | string | yes | The CB58-encoded block ID |
| encoding | string | — | Encoding format for the block (default: json) |
| network | string | — | Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
platform_get_block_by_height ~66
Get a P-Chain block by its height
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | — | Encoding format for the block (default: json) |
| height | string | yes | The block height as a string |
| network | string | — | Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
platform_get_blockchains ~90
Get all blockchains that exist on the P-Chain (paginated; use limit/offset)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max items to return (default: 50). Use with "offset" to page. |
| network | string | — | Avalanche network to query (default: mainnet) |
| offset | number | — | Number of items to skip from the start (default: 0). |
No output schema declared.
No examples provided.
platform_get_current_supply ~59
Get the current total supply of AVAX on a subnet
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
| subnetID | string | — | The subnet ID to query current supply for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_current_validators ~123
Get the current validators of a subnet (paginated; use limit/offset)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max items to return (default: 50). Use with "offset" to page. |
| network | string | — | Avalanche network to query (default: mainnet) |
| nodeIDs | array | — | Optional list of node IDs to filter by |
| offset | number | — | Number of items to skip from the start (default: 0). |
| subnetID | string | — | The subnet ID to query validators for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_height ~34
Get the current P-Chain block height
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
No output schema declared.
No examples provided.
platform_get_min_stake ~62
Get the minimum staking amounts for validators and delegators on a subnet
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
| subnetID | string | — | The subnet ID to query minimum stake for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_pending_validators ~124
Get the pending validators of a subnet (paginated; use limit/offset)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max items to return (default: 50). Use with "offset" to page. |
| network | string | — | Avalanche network to query (default: mainnet) |
| nodeIDs | array | — | Optional list of node IDs to filter by |
| offset | number | — | Number of items to skip from the start (default: 0). |
| subnetID | string | — | The subnet ID to query pending validators for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_staking_asset_id ~64
Get the asset ID of the token used for staking on a subnet
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
| subnetID | string | — | The subnet ID to query the staking asset for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_subnets ~96
Get information about subnets on the P-Chain
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | — | Optional list of subnet IDs to filter by |
| limit | number | — | Max items to return (default: 50). Use with "offset" to page. |
| network | string | — | Avalanche network to query (default: mainnet) |
| offset | number | — | Number of items to skip from the start (default: 0). |
No output schema declared.
No examples provided.
platform_get_total_stake ~58
Get the total amount staked on a subnet
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
| subnetID | string | — | The subnet ID to query total stake for (default: Primary Network) |
No output schema declared.
No examples provided.
platform_get_tx ~67
Get a P-Chain transaction by its transaction ID
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | — | Encoding format for the transaction (default: json) |
| network | string | — | Avalanche network to query (default: mainnet) |
| txID | string | yes | The CB58-encoded transaction ID |
No output schema declared.
No examples provided.
platform_get_tx_status ~51
Get the status of a P-Chain transaction
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | — | Avalanche network to query (default: mainnet) |
| txID | string | yes | The CB58-encoded transaction ID |
No output schema declared.
No examples provided.
platform_get_utxos ~97
Get UTXOs that reference a given set of P-Chain addresses
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | List of P-Chain addresses to get UTXOs for |
| limit | number | — | Maximum number of UTXOs to return |
| network | string | — | Avalanche network to query (default: mainnet) |
| sourceChain | string | — | If fetching atomic UTXOs, the chain they were exported from |
No output schema declared.
No examples provided.
platform_get_validators_at ~83
Get the validators and their weights of a subnet at a given P-Chain height
| Name | Type | Req | Description |
|---|---|---|---|
| height | — | yes | The P-Chain height to query validators at, or "proposed" |
| network | string | — | Avalanche network to query (default: mainnet) |
| subnetID | string | — | The subnet ID to query validators for (default: Primary Network) |
No output schema declared.
No examples provided.
rpc_lookup_method ~88
Look up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | — | RPC area to search. Defaults to all. |
| limit | number | — | Maximum number of results (default: 8) |
| query | string | yes | RPC method, namespace, or task to look up |
No output schema declared.
No examples provided.