Build on Robinhood Chain

Developer quickstart

Connect to Robinhood Chain with Ethereum tooling. Use the examples below to query the network and read ecosystem data through the HoodL2 API.

Robinhood Chain Mainnet

Chain ID
4663 (0x1237)
RPC
https://rpc.mainnet.chain.robinhood.com
Explorer
https://robinhoodchain.blockscout.com

Robinhood Chain Testnet

Chain ID
46630 (0xb626)
RPC
https://rpc.testnet.chain.robinhood.com
Explorer
https://explorer.testnet.chain.robinhood.com

The public RPC is free but rate-limited and, per Robinhood's terms, unsuitable for production. For real traffic, use a dedicated provider such as Alchemy, QuickNode, Blockdaemon, dRPC or Validation Cloud.

First call

Query the network

curl · eth_chainId
curl -s https://rpc.mainnet.chain.robinhood.com \
  -X POST -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# → {"jsonrpc":"2.0","id":1,"result":"0x1237"}  (4663)
TypeScript · viem
import { createPublicClient, http, defineChain } from "viem";

export const robinhoodChain = defineChain({
  id: 4663,
  name: "Robinhood Chain",
  // Gas is paid in ETH, like Ethereum — there is no separate chain token.
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: { default: { http: ["https://rpc.mainnet.chain.robinhood.com"] } },
  blockExplorers: { default: { name: "Blockscout", url: "https://robinhoodchain.blockscout.com" } },
});

const client = createPublicClient({ chain: robinhoodChain, transport: http() });
const block = await client.getBlockNumber();
Standard EVM tooling

Ethereum development tools

Robinhood Chain supports Ethereum development tools and the ERC-4337 and EIP-7702 account mechanisms. Check the chain documentation for compatibility differences and the contract registry for canonical EntryPoint addresses.

HoodL2 data

Read API · MCP · embeds

Read project records, categories, validators and metrics as JSON. The read API allows cross-origin requests and requires no key.

curl · /api/v1
curl -s https://hoodl2.com/api/v1
# → { name, entities, categories, validators, endpoints, … }

Read API

Read-only JSON at /api/v1. No auth. ETag + Cache-Control.

MCP server

Tools for AI agents: search_entities, get_entity, list_validators, get_metric.

Embeds

Drop-in entity cards and the validator board via iframe.

Read the OpenAPI schema for endpoint definitions. MCP clients connect to /api/mcp; the API index lists the JSON routes.

Write side

The filing API

Listings enter through /submit and are reviewed before publication. Authorized review agents can claim a submission, add corrected fields and sources, then record a recommendation and decision. Approval creates a public listing.

curl · agent review flow
# the queue
curl -s https://hoodl2.com/api/agent/submissions?status=open \
  -H "Authorization: Bearer $AGENT_API_KEY" -H "X-Agent-Name: my-reviewer"

# claim → enrich → decide
curl -s -X POST .../api/agent/submissions/$ID/claim -H "Authorization: Bearer $AGENT_API_KEY"
curl -s -X POST .../api/agent/submissions/$ID/enrich \
  -H "Authorization: Bearer $AGENT_API_KEY" -H "content-type: application/json" \
  -d '{"sources":[{"url":"https://…"}],"confidence":72,"recommendation":"approve"}'
curl -s -X POST .../api/agent/submissions/$ID/decision \
  -H "Authorization: Bearer $AGENT_API_KEY" -H "content-type: application/json" \
  -d '{"action":"approve"}'
EndpointDoes
POST /api/submissionsFile a listing (multipart; the public form uses it too).
POST /api/submissions/autofillScrape a project site into prefill suggestions + a captured logo.
GET /api/submissions/status/{token}Submitter-facing status + review ledger.
GET /api/agent/submissions?status=openThe review queue, newest first.
GET /api/agent/submissions/{id}One filing with its full event ledger.
POST /api/agent/submissions/{id}/claimOpen the filing for review.
POST /api/agent/submissions/{id}/enrichWrite the review payload.
POST /api/agent/submissions/{id}/decisionapprove · reject · needs_info. Approve lists the entity.

/api/agent/* wants Authorization: Bearer $AGENT_API_KEY and an X-Agent-Name header. Review actions are recorded under that name. Editors issue the keys; public endpoints use rate limits.

Drop-in widgets

Embed a widget

Choose a widget and copy its iframe code into your site. Widgets adapt to light and dark themes and include HoodL2 attribution. They require no API key or additional script.

Start typing to find a listed project.

Live preview

Embed code · iframe
Answers

Developer questions

What chain ID is Robinhood Chain?
Robinhood Chain mainnet is chain ID 4663 (0x1237), RPC https://rpc.mainnet.chain.robinhood.com. The public testnet is chain ID 46630 (0xb626), RPC https://rpc.testnet.chain.robinhood.com. Contracts written in Solidity or Vyper deploy without modification.
How do I pay for gas?
Gas is paid in ETH. Bridge ETH through a supported route and connect Ethereum-compatible tools to a Robinhood Chain RPC endpoint.
Does HoodL2 have an API?
Yes. The read-only JSON API at /api/v1 requires no key. The API index documents its endpoints; the developer page also provides MCP and widget references.