Quickstart for AI

A blockchain tool platform for AI agents, Nodit connects 70+ blockchain networks to AI through Skills, MCP, and llms.txt, and enables automated on-chain data access and transaction execution via the x402 protocol — without requiring an account.

Skills & MCP

AI-Native Integration

Connect Nodit APIs as tools to an AI agent via Skills or MCP. The agent understands the API structure and can call it directly, with x402 enabling payment through wallet signing alone — no account registration needed.

llms.txt

Instant Context

Adding llms.txt to the system prompt gives an AI immediate awareness of Nodit's API structure and supported chains. Documentation context can be delivered quickly without installing any tools.

70+ Networks

Unified Multichain API

Access 70+ blockchain networks through a consistent API interface — no need to implement separate client libraries or RPC specs per chain.

Node + Data + Event

Full-Stack Blockchain Access

Query real-time blockchain state via Node API, access indexed historical data through Web3 Data API, and receive on-chain events automatically via Webhook and Stream. The full spectrum of on-chain data is accessible from a single platform.

---

0. Prerequisites

At least one of the following must be in place before you begin.

• API Key-based calls: Sign up at the Nodit Console, create a project, and issue an API Key.
• x402-based calls: A wallet that supports EIP-712 signing and a USDC balance are required. APIs can be called using only a wallet, with no account registration needed.

Prepare your AI agent environment as well.

Path	Example Environments
Skills	Claude Code, Codex, Cursor, and other AI coding agents
MCP	Claude (web/desktop), Claude Code, Cursor, and other MCP clients

info

If you are using an AI coding agent, Skills is the right fit. For MCP client environments, use MCP. llms.txt can supplement either path, or serve as a way to review documentation context before installing any tools.

1. Choose an Execution Path: Skills or MCP

Connect an execution path so the AI agent can invoke Nodit APIs as tools.

1-1. Setting Up the Skills Path

Install Nodit Skills to give an AI coding agent access to Nodit API specifications and usage patterns.

• Nodit Skills GitHub Repository

Install Nodit Skills

# Install all skills
npx skills add noditlabs/skills --yes

# Install only the skills you need
npx skills add noditlabs/skills --skill web3-tools
npx skills add noditlabs/skills --skill web3-x402

web3-tools is the foundational skill that connects Nodit API structure and call patterns to the agent. web3-x402 handles payments via the x402 protocol. Installing both skills together lets an agent handle API calls and payments in a single workflow.

1-2. Setting Up the MCP Path

To use Nodit APIs as tools in an MCP client, connect to the Remote MCP server hosted by Nodit. The connection uses Streamable HTTP transport with OAuth login, so the API Key is never entered in a configuration file or URL.

• Nodit MCP Server GitHub Repository
• @noditlabs/nodit-mcp-server on npm

The Nodit MCP server provides tools for listing projects, listing APIs, retrieving specifications, and making actual calls.

Tool	Description
list_nodit_projects	List the Nodit projects that belong to the account
list_nodit_api_categories	List available API categories
list_nodit_node_apis	List Node APIs
list_nodit_data_apis	List Web3 Data APIs
list_nodit_webhook_apis	List Webhook APIs
list_nodit_aptos_indexer_api_query_root	List Aptos Indexer APIs
get_nodit_api_spec	Retrieve the detailed specification of a specific API
get_nodit_aptos_indexer_api_spec	Retrieve the detailed specification of the Aptos Indexer API
call_nodit_api	Call a Nodit API
call_nodit_aptos_indexer_api	Call the Aptos Indexer API

Adding the Connector in Claude (Web / Desktop)

The Remote MCP server automatically locates and uses an API Key from a project in the signed-in account. The following must therefore be in place.

• Nodit account: An account that can sign in to the Nodit Console
• At least one project in RUNNING status: With at least one API Key in ACTIVE status in that project
• MCP client: A client that supports Streamable HTTP and OAuth, such as Claude (web/desktop), Claude Code, or Cursor

In Claude, register the Remote MCP server as a custom connector.

1. Select Settings > Connectors > Add custom connector.
2. Enter Nodit in the connector search box. Confirm that the server URL matches https://mcp.nodit.io/mcp, then click [Connect] to add the connector.
3. Once the connector is added, the Nodit sign-in page opens. Sign in with your Nodit account and approve the permissions.
4. When the connection completes successfully, the Nodit MCP is available in Claude.

Adding the MCP in Claude Code

In Claude Code, register the server with the command below. The first time a tool is called in a session, a browser window opens and prompts you to sign in.

Claude Code MCP Registration

claude mcp add --transport http nodit https://mcp.nodit.io/mcp

If https://mcp.nodit.io/mcp is not entered exactly, a 401 error may occur.

To share the configuration at the project level, add the following to .mcp.json at the repository root.

.mcp.json

{
	"mcpServers": {
		"nodit": {
			"type": "http",
			"url": "https://mcp.nodit.io/mcp"
		}
	}
}

Adding to Cursor

In Cursor, add the server URL to ~/.cursor/mcp.json. A sign-in window opens on first use.

~/.cursor/mcp.json

{
	"mcpServers": {
		"nodit": {
			"url": "https://mcp.nodit.io/mcp"
		}
	}
}

Selecting a Project

The OAuth token identifies only the account. Because each API call consumes CU from a specific project, the project to use must be determined.

• If the account has one RUNNING project, that project is used automatically without any additional setting.
• If there are two or more, check the list with list_nodit_projects, and when calling call_nodit_api or call_nodit_aptos_indexer_api, add a prompt that identifies the project, such as "Query this using [project name]", so that the projectId is specified.
• projectId is the numeric ID shown in the console. The server retrieves the API Key directly from the project, so there is no need to pass the key to the model. To avoid exposing the key, not passing it is recommended.

Prompt Examples

Show me my Nodit projects.
Get the token balances of 0x... on Ethereum mainnet.
Using project 12345, get the latest block number on Polygon mainnet.

Common Issues

If a connection or call fails, check the table below for the matching symptom.

Symptom	Cause	Resolution
"Couldn't reach the MCP server"	Typo in the URL or missing /mcp path	Enter https://mcp.nodit.io/mcp exactly as shown
Repeated 401 even after signing in	The token has expired or was issued for another URL	Remove the connector, add it again, and sign in again
"This account has N usable projects, so 'projectId' is required"	Multiple projects exist but none was specified	Check with list_nodit_projects, then specify the project and retry
"Project N is not on this account"	A project ID from another account was entered	Use a project ID from your own account
"Project N is 'X', not RUNNING"	The project is stopped or deleted	Check the project status in the console, or specify another RUNNING project
"Project N has no active API key"	The project has no API Key in ACTIVE status	Issue an API Key in the console and retry
"This account has no Nodit projects"	No project has been created	Create a project in the console

Migrating from an Existing SSE Connection

The existing https://mcp.nodit.io/sse?apiKey=... method remains available for the time being. However, because the SSE transport has been deprecated in the MCP specification, Streamable HTTP is recommended for new connections. To migrate, remove the existing SSE connector and add a new one following the steps above. Since the API Key is no longer placed in the URL, the risk of key exposure is eliminated.

Local MCP Server (Optional)

Instead of the Remote server, the MCP server can also be run locally. This method passes the API Key as an environment variable rather than using OAuth.

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor IDE — ~/.cursor/mcp.json

Local MCP Server Config

{
	"mcpServers": {
		"nodit": {
			"command": "npx",
			"args": ["@noditlabs/nodit-mcp-server@latest"],
			"env": {
				"NODIT_API_KEY": "{YOUR_API_KEY}"
			}
		}
	}
}

Choosing Between Skills and MCP

Skills is better suited for applying Nodit usage patterns within an AI coding agent. MCP is the right choice when an MCP client needs to call Nodit APIs through a standard tool interface.

2. llms.txt (Optional)

llms.txt is not required when using Skills or MCP, since both paths already include Nodit API structure and usage context. You can add llms.txt as supplementary context in the following situations.

• You need to convey the Nodit documentation structure to an AI without installing any tools.
• You want to include an official documentation summary in a system prompt.
• You want to verify how well the AI understands Nodit before connecting Skills or MCP.

2-1. Locating llms.txt

Copy the content at the URL below, or configure your AI tool to reference it directly if it supports external document ingestion.

https://developer.nodit.io/llms.txt

2-2. Building a Basic Instruction Set for the AI

When using llms.txt, pairing the documentation summary with operational instructions improves the accuracy of the AI's responses. The example below is a minimal setup applicable to AI coding agents or custom agent runtimes.

System Prompt Example

You are working with Nodit, a multichain blockchain data platform.

Use Nodit's llms.txt as supporting context:
https://developer.nodit.io/llms.txt

When blockchain data is required:
1. Identify the relevant Nodit API category or method.
2. Prefer official Nodit tools or documented API patterns.
3. If the environment supports wallet-based payment, use x402 when API Key authentication is not available.
4. Explain which chain, network, and method you chose before making the request.

2-3. Verification Prompt Examples

After providing llms.txt, use prompts like the one below to confirm the AI understands Nodit API structure before connecting any tools.

Prompt Example

Use Nodit to find the latest Ethereum mainnet block.
Before calling anything, explain which Nodit API you would use and why.

3. Make Your First Call

With an execution path connected, use the example below to make a real API call — retrieving the latest block on Ethereum Mainnet.

3-1. Sample Prompt

The prompt below works with both Skills and MCP.

Prompt Example (Get latest block)

Use Nodit to get the latest block on Ethereum mainnet.
1. Identify the API category and method first.
2. Call the API.
3. Return the block number, block hash, and timestamp.

3-2. Expected Execution Flow

When configured correctly, the AI follows these steps.

1. Checks the Nodit API structure from the connected tool.
2. Selects the appropriate method from Web3 Data API or Node API.
3. Retrieves the API specification via Skills or MCP.
4. Authenticates using an API Key or x402 and sends the request.
5. Extracts and returns the relevant fields from the response.

4. Connect x402 Payment

Use x402 when API requests need to be processed using only a wallet signature, without an API Key. x402 is an HTTP 402 Payment Required-based payment protocol and is supported by Node API (JSON-RPC) and Web3 Data API.

4-1. How x402 Works

x402 receives payment conditions at request time, signs them, and resubmits the request.

1. The agent sends a request to a Nodit API.
2. Nodit returns 402 Payment Required along with payment conditions.
3. The agent signs the payment data using a wallet.
4. The agent resubmits the same request with the signed data included.
5. Nodit validates the payment and returns the API response.

4-2. Using x402 with Skills

web3-x402 is designed to work alongside web3-tools. web3-tools determines which API to call, while web3-x402 handles wallet authentication and payment processing.

x402 Prompt Example

Use Nodit to fetch the latest Ethereum mainnet block.
If API Key authentication is unavailable, use x402 payment.

info

x402 currently supports Node API (JSON-RPC) and Web3 Data API. The Webhook API and Aptos Node API cannot be called via x402. Supported chains and methods are listed in Supported APIs & Pricing.

4-3. Choosing a Payment Mode

x402 offers two modes depending on your call pattern. Start with Pay-Per-Use to validate behavior, then switch to Credit as call volume increases.

Mode	Description	Use Case
Pay-Per-Use (PPU)	USDC payment per request	Low-frequency calls, prototyping
Credit	Pre-loaded balance deducted per call	High-frequency calls, predictable workloads

For detailed differences and implementation steps, refer to the documents below.

• What is x402?
• How to use Pay-Per-Use
• How to use Credit

Next Steps

• Supported Chains — Feature coverage by chain, paid plan requirements, and testnet retention policy
• Web3 Data API — Query API backed by on-chain data indexing
• Webhook — Send notifications to a designated server when on-chain events occur
• Stream — Subscribe to on-chain events in real time over a persistent WebSocket channel
• What is x402? — Overview of the x402 protocol and payment flow
• Supported APIs & Pricing — List of chains and methods supported by x402

info

Create a project in the Nodit Console and issue an API Key to make your first API call.