A2A Agent Card · Sei

Sei Docs

Provider: Sei Card identifies: Sei Docs Conformance: Conformant Protocol: 0.3 Transport: HTTP+JSON Version: 1.0.0 Host: docs.sei.io Skills: 9
Discovery

An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.

https://docs.sei.io/.well-known/agent-card.json
Interfaces
https://docs.sei.io/ · transport · protocol HTTP+JSON non-standard interface list
Skills (9)

sei-bridges

Use when "bridge assets to Sei", "bridge assets from Sei", "launch an omnichain token on Sei", "deploy a LayerZero OFT on Sei", "send a cross-chain message with LayerZero", "get native USDC onto Sei", "use CCTP with Sei", "bridge with Wormhole on Sei", "IBC transfer to or from Sei", "why is IBC disabled on Sei", or "can I move ibc/ assets off Sei". Covers choosing and integrating Sei's documented EVM bridges — LayerZero V2 (OFT/OApp) and Circle CCTP v2 (native USDC) — plus the verify-first status of Wormhole, end-user bridge UIs, and the closed state of IBC in both directions, including what legacy ibc/ and Wormhole-wrapped balances can still do.

sei-contracts

Use when "deploy a smart contract on Sei", "set up Foundry for Sei", "set up Hardhat for Sei", "verify a contract on Seiscan", "write a Solidity contract for Sei", "make my Sei contract upgradeable", "optimize gas on Sei", "optimize my contract for Sei parallel execution", "what is the Sei gas model", "use ERC-4337 account abstraction on Sei", "why does my contract behave differently on Sei than Ethereum", "why does eth_blobBaseFee return an error on Sei", or "deploy a token on Sei". Covers EVM smart-contract development on Sei: Foundry/Hardhat setup, the Sei gas model, OCC parallel-execution-aware design, Seiscan verification via Sourcify, upgradeability, account abstraction, and the JSON-RPC methods that behave differently on Sei.

sei-frontend

Use when "build a Sei dApp frontend", "connect a wallet to Sei", "set up wagmi or viem for Sei", "configure Sei in wagmi", "use Sei Global Wallet for social login", "EIP-6963 wallet detection on Sei", "add MetaMask or Compass to my Sei app", "RainbowKit/ConnectKit with Sei", "show both sei1 and 0x addresses", "why is my Sei transaction stuck waiting for confirmations", "what gas price should the frontend send on Sei". Covers building Sei EVM dApp frontends: wagmi v2 + viem chain config, wallet integration, dual-address UX, legacy gas, and 400ms-finality UI patterns.

sei-migration

Use when "port an Ethereum dapp to Sei", "migrate an EVM contract to Sei", "migrate from Solana to Sei", "convert an Anchor program to Solidity for Sei", "why does my contract behave differently on Sei", "what breaks when I redeploy my Ethereum contract on Sei", or "translate Solana concepts like PDAs, CPI, SPL tokens, or rent to Sei EVM". Covers both migration paths: the Sei EVM behavioral deltas that break naive Ethereum ports (fee model, finality, opcode semantics, SSTORE cost, block tags) plus the frontend and deployment updates they require, and the Solana-to-Sei concept map with Anchor-to-Solidity translations, toolchain swaps, and OCC parallelization guidance.

sei-nodes

Use when "run a Sei full node", "set up a Sei RPC node", "become a Sei validator", "state sync my Sei node", "restore a Sei snapshot", "configure app.toml / config.toml for seid", "what hardware does a Sei node need", "move my node off RocksDB", "migrate to Giga storage / evm-ss-split", "my node panics because sc-enable is false", "enable a legacy sei_ JSON-RPC method", "my validator got jailed", or "my node won't sync past genesis". Covers running and operating Sei full nodes, RPC/archive nodes, and validators — bootstrapping, configuration, the SeiDB storage backend (mandatory state commit, Giga options, and the RocksDB removal), legacy JSON-RPC gating, and the validator lifecycle: keys, monitoring, and security.

sei-payments

Use when "accept USDC on Sei", "send USDC payment", "USDC contract address on Sei", "charge per API request", "HTTP 402 micropayments", "x402 on Sei", "monetize my API with crypto", "pay-per-call agent payments", "add a paywall to my endpoint", "stablecoin transfer on Sei". Covers accepting and sending payments on Sei with USDC (ERC-20, 6 decimals) and x402 v2 HTTP-native micropayments — token addresses, the transfer flow, and the upstream @x402 seller middleware and buyer clients.

sei-precompiles

Use when "call the Sei staking precompile", "delegate SEI from a contract", "vote on a Sei governance proposal in Solidity", "claim staking rewards via distribution precompile", "parse JSON on-chain on Sei", "verify a passkey/WebAuthn P256 signature on Sei", "associate my sei1 and 0x addresses", "look up the ERC20 pointer for a native or CW20 token", "register an EVM pointer for an existing CW20", "is the Sei oracle precompile still live", "can I still use the IBC precompile", "@sei-js/precompiles addresses and ABIs". Covers calling Sei's native precompiles (Staking, Governance, Distribution, JSON, P256, Addr, Bank, Pointer/PointerView, Solo) from Solidity and viem/ethers, which retired precompiles (Oracle, IBC) not to call, and cross-VM pointers for existing assets.

sei-security

Use when "is this safe to deploy on Sei", "how do I get randomness on Sei", "block.prevrandao isn't random", "simulate before sending a transaction", "verify address association before transfer", "secure a Sei smart contract", "wei vs usei in the staking precompile", "my AI agent is about to write on-chain", "pin the chainId before signing", "sanitize on-chain data before the LLM". Security patterns for Sei smart contracts and on-chain agents: testnet-first deployment, simulate-before-write, safe randomness, cross-VM address verification, precompile input and unit safety, and AI-agent guardrails.

sei-docs

Use when developers ask "How do I deploy a contract on Sei?", "How do I use Sei precompiles?", "What are the differences between Sei and Ethereum?", "How do I set up Foundry/Hardhat for Sei?", "How do pointer contracts work?", "How do I connect a wallet to Sei?", "What is the Sei MCP server?", "How do I bridge tokens on Sei?", "How do I run a Sei node?", "How do I stake via EVM?", "What is SSTORE gas on Sei?", "How do I verify my contract on Seiscan?", "How do I optimise gas on Sei?", "How do I use ERC-4337 on Sei?", "How do I make a contract upgradeable on Sei?", or any technical development question about building on Sei. Full developer reference playbook for docs.sei.io's audience.

Documentation
Evidence. Fetched 2026-10-26 from https://docs.sei.io/.well-known/agent-card.json, HTTP 200. The body was saved verbatim and is the sole source for everything on this page — no field is inferred. View the captured card. Providers change what they serve; if this card has moved or changed shape, the provider profile carries the current state as of the last build.

Work with this as data

Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for a2a agent cards

3 MCP tools reach this
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=seinetwork-io&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/seinetwork-io"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.