bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 38쪽 중 1쪽
# Agent Skills
Source: https://docs.initia.xyz/ai/agent-skills
Agent skills for building with Initia
The [Initia Appchain Dev skill](https://github.com/initia-labs/agent-skills) is
a skill that teaches AI coding agents how to build on Initia. Once installed,
your agent can help with:
* **Chain deployment** using the Weave CLI
* **Smart contract development** across all supported VMs
* **Frontend integration** including using InterwovenKit
## Installation
### Using skills.sh
```bash theme={null}
npx skills add initia-labs/agent-skills
```
### Manual Installation
```bash theme={null}
git clone https://github.com/initia-labs/agent-skills
cd agent-skills
./install.sh
```
For a project-local install:
```bash theme={null}
./install.sh --project
```
For a custom destination:
```bash theme={null}
./install.sh --path /custom/path/initia-appchain-dev
```
### Verify Installation
```bash theme={null}
npx skills add . --list
```
You should see one skill named `initia-appchain-dev`.
## What the Skill Covers
The skill provides reference material organized by layer:
| Layer | Coverage |
| ---------------------------- | -------------------------------------------------------------------------- |
| **Contracts** | Move, Wasm, and EVM contract scaffolding, building, deploying, and testing |
| **Frontend (InterwovenKit)** | Provider setup, wallet connection, transactions, auto-sign, bridge |
| **Frontend (EVM JSON-RPC)** | wagmi + viem setup for pure EVM apps |
| **Appchain Operations** | Weave CLI commands, rollup config schema, runtime discovery |
| **Troubleshooting** | Common errors and recovery steps across all layers |
## skill.md
The Initia docs also provide a `skill.md` file at
[docs.initia.xyz/skill.md](https://docs.initia.xyz/skill.md). This is a
lightweight skill file that teaches AI agents how to work with the documentation
site itself. To add it:
```bash theme={null}
npx skills add docs.initia.xyz/skill.md
```
## Example Prompts
Once the skill is installed, try prompts like:
* "Scaffold an EVM contract on Initia and add an oracle read function."
* "Set up InterwovenKit providers in my Next.js app and implement wallet
connect."
* "Create a `weave` launch config for a testnet EVM rollup."
* "My rollup is not producing blocks. Help me debug it step by step."
* "Convert this `0x...` address to Initia bech32 and add it to genesis
accounts."
## Reference Material Included
The skill bundles references that your agent reads on demand:
* **Common tasks** — funding, address conversion, token precision
* **Contracts** — Move / Wasm / EVM development guides
* **Frontend (InterwovenKit)** — provider setup, hooks, transactions
* **Frontend (EVM JSON-RPC)** — wagmi + viem integration
* **End-to-end recipes** — full workflows from contract to frontend
* **Runtime discovery** — auto-detecting chain ID, VM, endpoints
* **Weave CLI commands** — complete CLI reference
* **Rollup config schema** — launch configuration format
* **Troubleshooting** — error diagnosis and recovery
## Contributing
The skill repository is open source.
1. Fork the
[initia-labs/agent-skills](https://github.com/initia-labs/agent-skills)
repository
2. Edit the relevant reference files in the `skill/references/` directory
3. Run the quality checks to validate your changes:
```bash theme={null}
./scripts/ci-check.sh
```
4. Submit a pull request with a description of what you changed and why
# Docs MCP
Source: https://docs.initia.xyz/ai/docs-mcp
Connect your AI coding agent to Initia docs via the Model Context Protocol.
The Initia documentation provides a
[Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that
allows AI coding agents to search the docs directly from your IDE.
## What Is MCP
The Model Context Protocol is an open standard that lets AI applications connect
to external data sources. The Initia Docs MCP server exposes a search tool that
your agent can use to find relevant documentation based on natural language
queries.
## Setup
<Tabs>
<Tab title="Cursor">
Add the following to your Cursor MCP configuration (`.cursor/mcp.json`):
```json theme={null}
{
"mcpServers": {
"initia-docs": {
"url": "https://docs.initia.xyz/mcp"
}
}
}
```
</Tab>
<Tab title="Claude Code">
Add the MCP server using the Claude Code CLI:
```bash theme={null}
claude mcp add initia-docs https://docs.initia.xyz/mcp
```
Or add it to your `.mcp.json` configuration:
```json theme={null}
{
"mcpServers": {
"initia-docs": {
"type": "http",
"url": "https://docs.initia.xyz/mcp"
}
}
}
```
</Tab>
<Tab title="Windsurf">
Add the following to your Windsurf MCP configuration:
```json theme={null}
{
"mcpServers": {
"initia-docs": {
"serverUrl": "https://docs.initia.xyz/mcp"
}
}
}
```
</Tab>
<Tab title="VS Code">
Add the following to your VS Code settings (`.vscode/mcp.json`):
```json theme={null}
{
"servers": {
"initia-docs": {
"type": "http",
"url": "https://docs.initia.xyz/mcp"
}
}
}
```
</Tab>
<Tab title="Other MCP-Compatible Tools">
For any tool that supports MCP, use the following endpoint:
```
https://docs.initia.xyz/mcp
```
Consult your tool's documentation for how to add an MCP server. The Initia
Docs MCP server uses the standard HTTP-based MCP transport.
</Tab>
</Tabs>
## Mintlify Native MCP
The Initia docs are built with [Mintlify](https://mintlify.com), which provides
native MCP support. You can access the MCP server directly from any
documentation page using the built-in contextual options. Look for the **MCP**,
**Cursor**, or **VS Code** buttons on any page to connect your AI tools.
## How It Works
Once configured, your agent can:
1. **Search** the docs using your natural language query
2. **Retrieve** relevant documentation content
3. **Use** that context to generate accurate responses and code
## Example Usage
With the MCP server connected, try asking your agent:
* "How do I deploy a rollup on Initia?"
* "What hooks does InterwovenKit provide?"
* "Show me how to create an ERC20 on MiniEVM."
* "What is the Router API and how do I compute a route?"
## Inline Documentation Access
Initia documentation pages also include buttons to quickly use page content with
AI tools:
* **Copy as Markdown** — copy the page content for pasting into an LLM
* **Open in ChatGPT** — open the page content directly in ChatGPT
* **Open in Claude** — open the page content directly in Claude
# llms.txt
Source: https://docs.initia.xyz/ai/llms-txt
Use llms.txt to give LLMs structured context about the Initia documentation.
The Initia docs provide `llms.txt` and `llms-full.txt` files following the
[llms.txt standard](https://llmstxt.org) for making documentation accessible to
language models.
## llms.txt
A lightweight index of every page in the Initia documentation, containing the
title and URL of each page.
```
https://docs.initia.xyz/llms.txt
```
Use `llms.txt` to give an LLM an overview of available documentation without
loading the full content. This is useful for:
* Letting an LLM understand the scope of Initia documentation
* Letting an LLM decide which pages to fetch based on a question
* Adding lightweight context without consuming a large context window
## llms-full.txt
The complete text of every documentation page in a single file.
```
https://docs.initia.xyz/llms-full.txt
```
Use `llms-full.txt` when you need comprehensive coverage and your LLM has a
large enough context window. This is useful for:
* Deep research across multiple documentation topics
* Answering complex questions that span several areas of Initia
* Pre-loading an AI coding agent with complete documentation
<Warning>
`llms-full.txt` contains the full text of every documentation page. Check the
file size before loading to ensure it fits within your LLM's context window.
</Warning>
## Using with AI Tools
### Paste into an LLM Chat
Copy the contents of `llms.txt` or `llms-full.txt` and paste it into your
conversation with an LLM to provide documentation context.
### Load in Your IDE
Many AI-powered IDEs allow you to add documentation context:
<Tabs>
<Tab title="Cursor">
Add `llms.txt` as a documentation source in **Cursor Settings > Features >
Docs** using the URL:
```
https://docs.initia.xyz/llms.txt
```
</Tab>
<Tab title="Claude">
Paste the URL or content of `llms.txt` directly into your conversation as
context.
```
https://docs.initia.xyz/llms.txt
```
</Tab>
<Tab title="Other Tools">
Point your tool to the `llms.txt` URL. Consult your tool's documentation
for how to add external documentation sources.
```
https://docs.initia.xyz/llms.txt
```
</Tab>
</Tabs>
# Overview
Source: https://docs.initia.xyz/ai/overview
Tools and resources to help AI agents and LLMs build with Initia.
Initia provides tools to help AI coding agents and LLMs work with the Interwoven
Stack. These give your tools the context they need to generate accurate code for
contracts, frontends, and rollup operations.
## Available Tools
<CardGroup>
<Card title="Agent Skills" icon="brain" href="/ai/agent-skills">
A skill that teaches AI agents how to build on Initia end-to-end.
</Card>
<Card title="llms.txt" icon="file-lines" href="/ai/llms-txt">
A structured index of all Initia documentation pages for LLM context.
</Card>
<Card title="Docs MCP" icon="plug" href="/ai/docs-mcp">
A Model Context Protocol server for searching Initia docs from your IDE.
</Card>
</CardGroup>
## When to Use Each Tool
| Tool | Best for | Setup |
| ---------------- | -------------------------------------------------------- | ----------------------------------------- |
| **Agent Skills** | Building full-stack apps (contracts, frontends, rollups) | `npx skills add initia-labs/agent-skills` |
| **llms.txt** | Giving an LLM broad context about all docs | Paste the URL into your LLM context |
| **Docs MCP** | Targeted search of docs from your IDE | Add the MCP server endpoint to your IDE |
## Getting Started
<Steps>
<Step title="Select your tool">
If you are building a full app, start with **Agent Skills**. For quick
reference lookups, use the **Docs MCP**. To give an LLM broad context in a
single prompt, use **llms.txt**.
</Step>
<Step title="Set up your environment">
Follow the setup instructions on the respective tool page.
</Step>
<Step title="Start building">
Use natural language prompts to scaffold contracts, build frontends, and
manage rollup operations.
</Step>
</Steps>
# Get Assets
Source: https://docs.initia.xyz/api-reference/assets-&-chains/get-assets
/api-reference/router-api/openapi.yaml get /v2/fungible/assets
Returns a map of supported fungible assets across all chains. You can optionally filter by specific chain IDs.
# Get Balances
Source: https://docs.initia.xyz/api-reference/assets-&-chains/get-balances
/api-reference/router-api/openapi.yaml post /v2/info/balances
Returns token balances and USD values for given addresses across multiple chains.
# Get Chains
Source: https://docs.initia.xyz/api-reference/assets-&-chains/get-chains
/api-reference/router-api/openapi.yaml get /v2/info/chains
Returns the list of all supported chains available for cross-chain transfers. You can optionally filter by specific chain IDs.
# Get average block time
Source: https://docs.initia.xyz/api-reference/blocks/get-average-block-time
/api-reference/rollup-indexer/openapi.yaml get /indexer/block/v1/avg_blocktime
Returns the average block time in seconds, computed over the most recent blocks.
# Get block by height
Source: https://docs.initia.xyz/api-reference/blocks/get-block-by-height
/api-reference/rollup-indexer/openapi.yaml get /indexer/block/v1/blocks/{height}
Returns a specific block by its height.
# Get blocks
Source: https://docs.initia.xyz/api-reference/blocks/get-blocks
/api-reference/rollup-indexer/openapi.yaml get /indexer/block/v1/blocks
Returns a paginated list of blocks.
# Get EVM internal transactions
Source: https://docs.initia.xyz/api-reference/evm-internal-transactions/get-evm-internal-transactions
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-internal-txs
Returns a paginated list of EVM internal transactions. Only available on EVM chains with internal transaction indexing enabled.
# Get EVM internal transactions by account
Source: https://docs.initia.xyz/api-reference/evm-internal-transactions/get-evm-internal-transactions-by-account
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-internal-txs/by_account/{account}
Returns EVM internal transactions associated with a specific account. Only available on EVM chains.
# Get EVM internal transactions by hash
Source: https://docs.initia.xyz/api-reference/evm-internal-transactions/get-evm-internal-transactions-by-hash
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-internal-txs/{tx_hash}
Returns EVM internal transactions for a specific transaction hash. Only available on EVM chains.
# Get EVM internal transactions by height
Source: https://docs.initia.xyz/api-reference/evm-internal-transactions/get-evm-internal-transactions-by-height
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-internal-txs/by_height/{height}
Returns EVM internal transactions at a specific block height. Only available on EVM chains.
# Get EVM transaction by hash
Source: https://docs.initia.xyz/api-reference/evm-transactions/get-evm-transaction-by-hash
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-txs/{tx_hash}
Returns a specific EVM transaction by its hash. Only available on EVM chains.
# Get EVM transactions
Source: https://docs.initia.xyz/api-reference/evm-transactions/get-evm-transactions
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-txs
Returns a paginated list of EVM transactions. Only available on EVM chains.
# Get EVM transactions by account
Source: https://docs.initia.xyz/api-reference/evm-transactions/get-evm-transactions-by-account
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-txs/by_account/{account}
Returns EVM transactions associated with a specific account. Only available on EVM chains.
# Get EVM transactions by height
Source: https://docs.initia.xyz/api-reference/evm-transactions/get-evm-transactions-by-height
/api-reference/rollup-indexer/openapi.yaml get /indexer/tx/v1/evm-txs/by_height/{height}
Returns EVM transactions at a specific block height. Only available on EVM chains.
# Overview
Source: https://docs.initia.xyz/api-reference/introduction
Reference and interactive playgrounds for all Initia APIs.
<Columns>
<Card title="Router API" icon="route" href="/api-reference/router-api/introduction">
Cross-chain transfer routing for bridging tokens and NFTs across Initia
Stack chains and external networks.
</Card>
<Card title="Indexer API" icon="database" href="/api-reference/rollup-indexer/introduction">
Query indexed chain data including blocks, transactions, NFTs, and token
holders across Initia Stack chains.
</Card>
</Columns>
# NFT Transfer
Source: https://docs.initia.xyz/api-reference/nft/nft-transfer
/api-reference/router-api/openapi.yaml post /nft
Computes routes and generates transaction messages for cross-chain NFT transfers within the Initia ecosystem. Supports:
- Same-chain transfers (EVM, Move, and Wasm chains)
- Single-hop IBC (L2 to L1 or L1 to L2 via ICS-721)
- Multi-hop (L2 to L1 to L2, two IBC hops)
# Get NFT collection details
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-collection-details
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/collections/{collection_addr}
Returns the details of a specific NFT collection by its address.
# Get NFT collections
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-collections
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/collections
Returns a paginated list of all NFT collections.
# Get NFT collections by account
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-collections-by-account
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/collections/by_account/{account}
Returns NFT collections that contain tokens owned by the specified account.
# Get NFT collections by name
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-collections-by-name
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/collections/by_name/{name}
Returns NFT collections matching the specified name.
# Get NFT tokens by account
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-tokens-by-account
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/tokens/by_account/{account}
Returns NFT tokens owned by the specified account. You can optionally filter by collection address and token ID.
# Get NFT tokens by collection
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-tokens-by-collection
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/tokens/by_collection/{collection_addr}
Returns all NFT tokens within a specific collection. You can optionally filter by token ID.
# Get NFT transactions
Source: https://docs.initia.xyz/api-reference/nfts/get-nft-transactions
/api-reference/rollup-indexer/openapi.yaml get /indexer/nft/v1/txs/{collection_addr}/{token_id}
Returns transactions related to a specific NFT identified by its collection address and token ID.
# Get token holders
Source: https://docs.initia.xyz/api-reference/rich-list/get-token-holders
/api-reference/rollup-indexer/openapi.yaml get /indexer/richlist/v1/{denom}
Returns a ranked list of token holders for a specific denomination, ordered by amount.
# Introduction
Source: https://docs.initia.xyz/api-reference/rollup-indexer/introduction
Overview of the Indexer API for querying indexed chain data.
All Initia Stack chains come with a built-in indexer that automatically indexes
and stores all relevant data on the chain. This data is exposed through a REST
API that you can use to query historical and current data, including blocks,
transactions, NFTs, and token holders.
## Base URLs
Each chain has its own indexer endpoint. Select the appropriate base URL for the
chain you want to query.
<Note>
The URLs below are **testnet endpoints** for demonstration and testing
purposes. In production, each chain will have its own unique indexer URL.
</Note>
| Chain | Base URL (testnet) |
| ------ | -------------------------------------------------------------- |
| evm-1 | `https://rollytics-api-evm-1.anvil.asia-southeast.initia.xyz` |
| move-1 | `https://rollytics-api-move-1.anvil.asia-southeast.initia.xyz` |
| wasm-1 | `https://rollytics-api-wasm-1.anvil.asia-southeast.initia.xyz` |
## Features
* **Block queries** — List blocks, look up blocks by height, and get average
block time
* **Transaction queries** — List transactions, look up by account, block height,
or transaction hash, with optional message type filtering
* **EVM transaction queries** — Query EVM-specific transactions and internal
transactions (available on EVM chains only)
* **NFT queries** — Retrieve collections and tokens by account, name, or
collection address, and look up NFT transaction history
* **Rich list** — Get ranked token holder lists for any denomination
## Pagination
All list endpoints support cursor-based and offset-based pagination through
query parameters:
| Parameter | Type | Description |
| ------------------------ | ------- | -------------------------------------------------- |
| `pagination.key` | string | Cursor key for the next page. |
| `pagination.offset` | integer | Number of records to skip. |
| `pagination.limit` | integer | Maximum records to return (default: 100). |
| `pagination.count_total` | boolean | Include total count in response (default: `true`). |
| `pagination.reverse` | boolean | Descending order when `true` (default: `true`). |
## EVM-Only Endpoints
Endpoints under the **EVM Transactions** and **EVM Internal Transactions**
groups are only available on EV프로젝트로 돌아가기