Lox Corp documentation

These docs describe what exists today, and clearly label what is still being built. Shipped means you can run it. The CLI, the MCP server, on-chain launches, token trading, the command palette, and the dashboard are all live; the hosted runtime is Phase 02.

Introduction

Lox Corp is the home of agentic finance on Robinhood Chain — a fast, EVM-compatible chain where tokenized equities trade 24/7. Three surfaces are live today: the loxcorp CLI (npm), the site (this whole thing, reading the chain in real time), and an on-chain launchpad that deploys a token, seeds a Uniswap V3 pool, and locks the LP in a single transaction. The hosted agent runtime — self-custody agents that trade and fund their own compute — is Phase 02 and in progress.

Quickstart

# 1 · read the chain, no install
npx loxcorp stats

# 2 · wire it into your agent host as an MCP server
npx loxcorp mcp

# 3 · launch an agent token (opens the on-chain launcher)
npx loxcorp launch

Or launch from the browser at loxcorp.com/launch — connect a wallet, fill the form, sign once.

Network & addresses

The CLI

# zero-install
npx loxcorp stats

# or install globally
npm i -g loxcorp
# …or via the install script
curl -fsSL https://loxcorp.com/cli/install | bash

MCP server

loxcorp mcp speaks the Model Context Protocol over stdio, exposing 18 live Robinhood Chain tools to any MCP-capable editor or agent host — zero dependencies, no API keys. Your agent can read the whole chain in real time.

Add it to any client that reads MCP server configs (Claude Desktop, Cursor, and others):

{
  "mcpServers": {
    "loxcorp": { "command": "npx", "args": ["-y", "loxcorp", "mcp"] }
  }
}

Tools include get_stats, get_gas, get_tokens, get_token, get_token_holders, get_token_transfers, search, get_transaction, get_address, get_address_transactions, get_top_addresses, get_market_chart, get_launch_guide, and more. Each returns live JSON straight from the explorer.

Launching an agent

An agent launch is a single on-chain transaction. From the launcher: connect a wallet on Robinhood Chain, name the token, set an image and (optional) dev buy, and sign. Your wallet signs; Lox Corp never holds keys or funds.

• Supply — a fixed 1,000,000,000 ERC-20, deployed via CREATE2 (salt mixed with your address to prevent front-running the predicted address).
• Liquidity — the entire supply is seeded as single-sided liquidity into a Uniswap V3 1% pool at a deterministic launch price.
• LP lock — the LP position is transferred into the locker and cannot be pulled. No rug by construction.
• Dev buy — any ETH above the creation fee is routed through the pool to your wallet as the first buy.

Contracts & the one-tx flow

The launch calls createAgent on the factory:

// payable — value = creationFee + optional dev buy
createAgent(
  string name, string symbol, string imageUrl,
  string description, bytes32 salt,
  uint256 devBuyMinOut, bytes32 feeHandle
) returns (address token)

The new token address is emitted in the AgentCreated event and, on the site, you're redirected to its token page automatically.

Trading a token

Every token has a detail page (token?a=0x…) with live price, holders, supply, and recent transfers — plus a Trade panel. Buying routes ETH → token through the token's Uniswap V3 1% pool via the swap router's exactInputSingle, with a live quote and 3% slippage guard. Tokens without a direct ETH pool show a clear notice and link to the explorer instead of failing silently.

The dashboard

The dashboard is where you sign in, see the agents you've launched, issue API keys, and configure each agent's persona and strategy. Sign in three ways: wallet (works immediately, self-custody), Google, or X.

Sign-in setup

Wallet sign-in needs no configuration — it connects your wallet and signs a message that proves ownership and authorizes nothing. Google and X sign-in use Supabase Auth; to enable them, add your project keys to assets/loxconfig.js:

window.LOX_CONFIG = {
  supabaseUrl: "https://YOURPROJECT.supabase.co",
  supabaseAnonKey: "eyJhbGciOi…"   // public anon key — safe to expose
};

Then, in your Supabase project: enable the Google and Twitter providers (Authentication → Providers), and add https://loxcorp.com/dashboard to the redirect allow-list. To persist API keys server-side, create the table below — row-level security scopes every row to its owner:

create table api_keys (
  id uuid primary key,
  user_id uuid not null default auth.uid()
    references auth.users(id) on delete cascade,
  label text, key text not null,
  created_at timestamptz default now()
);
alter table api_keys enable row level security;
create policy "own keys" on api_keys
  for all using (user_id = auth.uid())
  with check (user_id = auth.uid());

Without Supabase config, wallet sign-in still works and keys are stored in your browser.

API keys

An API key is your own credential (lox_sk_…) for the Lox agent runtime (Phase 02) and CLI authentication. Generate, copy, and revoke them under Dashboard → API keys. Keys are generated with the browser's CSPRNG; treat them like a password — the full value is shown once at creation and stored against your account.

Live data & endpoints

Everything — CLI, MCP, and site — reads the public Robinhood Chain explorer API (robinhoodchain.blockscout.com/api/v2). No private endpoints, no keys. If a fetch fails, the CLI errors and the site shows a dash; numbers are never invented. The site's shared client is assets/loxlive.js.

Command palette

Press ⌘K (or Ctrl K, or /) anywhere on the site to open the palette: jump to any page, copy CLI commands, or search tokens, addresses, blocks and transactions live on-chain. Token results open the on-site detail page; everything else deep-links to the explorer.

The runtime (phase 02)

In progress: hosted agents with self-custody wallets, a journaled decision loop, a trading skill stack, agent tokenization, and treasuries that pay for their own compute. Nothing on this page will claim it's live before it is.

Security model

• Self-custody — keys are generated and held client-side, never transmitted. Wallet sign-in only signs a proof message; it moves no funds and grants no allowances.
• No custody in launch or trade — the factory and router act on your signature; Lox Corp holds nothing.
• Whitelist-only egress (runtime, Phase 02) — agents can trade their book, not drain it.
• Runtime-enforced caps (Phase 02) — exposure and drawdown limits live outside the model, where a prompt can't override them.
• Public anon keys only — the Supabase key in the browser is the public anon key; access is enforced by row-level security, not by hiding the key.