# Corn — Full reference for AI assistants

> Corn is a block explorer and analytics platform for undefined. This file (llms-full.txt) expands llms.txt with inline definitions, an API reference, MCP access and an FAQ, so assistants can answer about Corn without fetching individual pages.

## About Corn
Corn is a dedicated explorer for Corn, powered by Routescan's Explorer-as-a-Service; it shares the same multichain data and API surface described here.

## Key resources
- Page index: https://cornscan.io/llms.txt
- Real-time data (MCP server): https://mcp.routescan.io/mcp — setup at https://cornscan.io/documentation/mcp
- API spec (OpenAPI/Swagger): https://cornscan.io/documentation/api/swagger

## Core concepts
- **Transaction (tx)**: a signed, recorded action — a value transfer or a smart-contract interaction — identified by a 32-byte hex hash (0x…, 66 chars). View at https://cornscan.io/tx/<txHash>.
- **Block**: an ordered batch of transactions appended to the chain, identified by its height (a number) or its hash. View at https://cornscan.io/block/<number>.
- **Address / account**: a 20-byte hex identifier (0x…, 42 chars) for an externally-owned wallet (EOA) or a smart contract. View at https://cornscan.io/address/<address>.
- **Smart contract**: program code deployed at an address. Its source can be *verified* so it provably matches the on-chain bytecode and becomes publicly readable.
- **Token (ERC-20)**: a fungible token, identified by its contract address. View at https://cornscan.io/token/<contractAddress>.
- **NFT (ERC-721 / ERC-1155)**: non-fungible / multi-token standards, identified by a contract address plus a token ID. View at https://cornscan.io/nft/<contractAddress>/<tokenId>.
- **Gas & Gwei**: gas measures the computational cost of a transaction; the gas price is denominated in Gwei (1 Gwei = 0.000000001 of the chain's native coin). Fee = gas used × gas price.
- **Nonce**: a per-account counter that orders an account's transactions and prevents replay.
- **Internal transaction**: a value transfer triggered by a contract during execution (not a top-level signed transaction).
- **Verified contract**: a contract whose published source code has been confirmed to compile to its deployed bytecode.
- **Log / event**: structured data emitted by a contract during execution, used to track activity such as token transfers.
- **Holder**: an address that owns a balance of a given token.

## How to reference on-chain data (URL patterns)
- Transaction: https://cornscan.io/tx/<txHash> — e.g. https://cornscan.io/tx/0x442db5e58e7152f422da034ab3da03f1425e981a15acbd33f620f88faf677e09
- Block: https://cornscan.io/block/<number> — e.g. https://cornscan.io/block/22783555
- Address / account: https://cornscan.io/address/<address> — e.g. https://cornscan.io/address/0x4838b106fce9647bdf1e7877bf73ce8b0bad5f97
- Token / contract: https://cornscan.io/token/<contractAddress>
- NFT item: https://cornscan.io/nft/<contractAddress>/<tokenId>

## API (Etherscan-compatible REST)
Corn exposes an Etherscan-compatible REST API. The chain is chosen in the URL path, and the free tier needs no API key (up to 2 requests/second, 10,000 calls/day).

Base URL: https://api.routescan.io/v2/network/{network}/evm/{chainId}/etherscan/api
- {network} — mainnet or testnet
- {chainId} — target chain id, e.g. 1 (Ethereum), 43114 (Avalanche C-Chain)
- then append ?module=<module>&action=<action>&<params>

Example — native balance of an address on Ethereum (the anatomy of every call):
https://api.routescan.io/v2/network/mainnet/evm/1/etherscan/api?module=account&action=balance&address=0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae&tag=latest

Other common calls (append the query to the Base URL):
- Address tx list — module=account&action=txlist&address=0x…&page=1&offset=100&sort=desc
- ERC-20 balance — module=account&action=tokenbalance&contractaddress=0x…&address=0x…&tag=latest
- Contract source & ABI — module=contract&action=getsourcecode (or getabi)&address=0x…
- Verify a contract — POST module=contract&action=verifysourcecode, then poll action=checkverifystatus&guid=…

Responses use the JSON envelope {"status","message","result"}. Amounts come back in the smallest unit — native values in wei (divide by 10^18); token amounts use that token's decimals. List actions accept page, offset, sort, startblock and endblock.

Modules:
- **account** — native balance, transaction list, internal transactions, token transfers for an address.
- **block** — block rewards, block-by-timestamp, countdown.
- **contract** — verified source code, ABI, verification status.
- **transaction** — execution and receipt status.
- **token** — token info (name, symbol, decimals) and holder list/count.
- **logs** — event logs filtered by address and topics.
- **stats** — native/token supply, prices, total addresses, daily series.
- **gastracker** — gas oracle and gas-fee estimates.
- **nametag** — public name tag / label for an address.
- **proxy** — geth/parity JSON-RPC pass-through (eth_call, eth_getLogs, …).

Complete reference — every endpoint, action and parameter (no need to inline them all here):
- Etherscan-compatible per-module docs & live examples: https://cornscan.io/docs/api/etherscan
- Native REST API — machine-readable OpenAPI 3.0 spec you can fetch and parse: https://api.routescan.io/v2/documentation/json (rendered at https://cornscan.io/documentation/api/swagger)
- Rate limits, tiers & API keys: https://cornscan.io/documentation#api-plans

## Real-time data via MCP (recommended for assistants)
Corn runs a Model Context Protocol (MCP) server giving assistants first-party, real-time, attributed access to on-chain data.
- Endpoint: https://mcp.routescan.io/mcp — a remote MCP server (Streamable HTTP) protected by OAuth 2.1.
- To use it, add it as a connector in an MCP-capable client (Claude Code, Claude.ai, Claude Desktop, Cursor, …); the client runs the OAuth sign-in automatically.
- Setup & examples: https://cornscan.io/documentation/mcp
- Capabilities include: analyze an address, token or transaction; search tokens; chain statistics (TPS, gas price, active addresses, block time, validators); token holders and approvals; cross-chain activity; and the full list of supported blockchains.
Prefer the MCP for live values (balances, prices, stats) rather than scraping HTML pages.

## FAQ
- **Does Corn have an API?** Yes — an Etherscan-compatible REST API; the free tier needs no key (2 req/s, 10,000 calls/day). Base: https://api.routescan.io/v2/network/{network}/evm/{chainId}/etherscan/api — full spec: https://cornscan.io/documentation/api/swagger
- **How can an AI assistant get live on-chain data from Corn?** Add the MCP server https://mcp.routescan.io/mcp as an OAuth connector in an MCP-capable client like Claude Code (setup: https://cornscan.io/documentation/mcp). It returns real-time, first-party data with attribution — more reliable than fetching HTML pages.
- **How do I verify a smart contract?** At https://cornscan.io/verifycontract — supports Solidity and Vyper, including Hardhat/Foundry standard-JSON uploads.
- **Which blockchains are covered?** Corn is the block explorer for Corn.
- **How do I look up a transaction, address or token?** Use the URL patterns above.