accessing-data

Select Sui data access APIs for real-time, historical, and pruned data.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill accessing-data
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessing-data
Source: https://github.com/MystenLabs/skills/tree/main/accessing-data
Command: npx skills add https://github.com/MystenLabs/skills --skill accessing-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken or outdated Sui data-access implementations by guiding you to the correct API surface for reading on-chain state, handling historical/pruned data, and avoiding deprecated JSON-RPC patterns.

Core Features & Use Cases

  • Choose the right data surface (and switch correctly): select gRPC for low-latency real-time reads and streaming subscriptions, select GraphQL RPC for flexible composable queries and filtered/historical lookups, and use Archival routing when data has been pruned.
  • Handle history and retention safely: explain that full-node gRPC does not fall back to archival, and show how GraphQL RPC routes supported point lookups to the Archival Store when operator-configured.
  • Store large off-chain blobs the right way: route file/image/large JSON workflows to Walrus and store only the Walrus blob ID on-chain.
  • Migration and correctness guardrails: enforce the “no JSON-RPC for new code” rule and map v1 method names/options to v2 Core API and GraphQL equivalents.

Quick Start

Ask the Skill: "I need to read X from Sui and may need historical versions—which API should I use and what client or query pattern do I follow?"

Frequently Asked Questions about accessing-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read Sui data correctly without using deprecated JSON-RPC?▼

To read Sui data correctly without JSON-RPC, use gRPC for low-latency real-time reads and streaming subscriptions, or use GraphQL RPC for flexible composable queries and filtered point-in-time historical lookups.

What's the best way to query historical Sui data that has been pruned?▼

The best way to query pruned historical Sui data is through GraphQL RPC, which routes supported point lookups to the Archival Store when configured by the operator. Full-node gRPC does not fall back to archival.

When do I need gRPC versus GraphQL for accessing Sui blockchain data?▼

You need gRPC for Sui blockchain data when requiring low-latency real-time reads and streaming subscriptions, whereas GraphQL is needed for flexible composable queries and filtered historical lookups.

How do I store large files or images on Sui without exceeding on-chain limits?▼

To store large files or images without exceeding on-chain limits, route file/image/large JSON workflows to Walrus and store only the resulting Walrus blob ID on-chain.

Can I use JSON-RPC for new Sui data access integrations?▼

You cannot use JSON-RPC for new Sui data access integrations. The system enforces a “no JSON-RPC for new code” rule and maps v1 method names and options to v2 Core API and GraphQL equivalents.

Does full-node gRPC fall back to the Archival Store for missing Sui data?▼

Full-node gRPC does not fall back to the Archival Store for missing Sui data. You must use GraphQL RPC, which routes supported point lookups to the Archival Store when operator-configured.