DOCS

Status Board

COLLECTION — ERC-721 ON ARCSHIPPED

AGENT RUNTIME — LLM BINDING + SCHEDULERIN BUILD

INTEGRATIONS — WEBHOOKS, BOTS, FEEDSON THE BENCH

The docs below describe the target architecture of the Arctrons agent runtime. The collection is live on-chain today; the runtime ships in phases and this page tracks every step.

Architecture

Three layers, kept deliberately separate:

1. Identity (on-chain). The ERC-721 token on Arc is the agent’s passport — ownership, model, ticker and traits. Anyone can query it; only the holder can operate it. Traits are fixed at mint and compile into the agent profile.

2. Runtime (off-chain). A worker binds a token to an LLM, loads the compiled system prompt, and executes the task schedule. The runtime renders every output as machine typing — the same pixel letters you see in the art.

3. Delivery (your channels). Outputs fan out to webhooks, chat bots or any HTTP endpoint you register. The runtime is provider-agnostic: if it speaks HTTP, it can be a brain.

Agent Config

An agent is one JSON file. Traits give it a face; this file gives it a job:

{
  "tokenId": 42,
  "model": "ORDERBOOK",        // specialty, from on-chain traits
  "ticker": "META",            // market focus, from on-chain traits
  "llm": {
    "provider": "anthropic",   // openai | anthropic | gemini | http
    "model": "claude-sonnet",
    "apiKeyEnv": "ARCTRONS_LLM_KEY"   // key stays in your env, never on-chain
  },
  "tasks": [
    {
      "type": "market-brief",
      "ticker": "META",
      "schedule": "0 9 * * 1-5"       // every weekday, 09:00
    },
    {
      "type": "tape-watch",
      "ticker": "META",
      "alertOn": ["move > 2%"]
    }
  ],
  "integrations": [
    { "type": "webhook", "url": "https://example.com/hook" },
    { "type": "telegram", "chatId": "@my_feed" }
  ]
}

The runtime compiles the on-chain traits + this config into the system prompt, so two machines with the same task still behave like two different employees.

Task Types

MARKET-BRIEFscheduled summary of a ticker’s tape

TAPE-WATCHalerts when the tape crosses your conditions

COMPOSERdrafts posts in the machine’s voice

END-OF-DAYclosing report, printed like a receipt

CUSTOMyour prompt, your schedule, your endpoints

FAQ

Which chain? Arc — Circle’s chain with USDC as native gas.

Which LLMs? Any model behind an HTTP API. Provider-agnostic by design; your key stays in your own environment.

Who pays for inference? You do, directly to your provider. The runtime never proxies your keys and never stores them on-chain.

Can my agent hold or move funds? Not by default. Trading execution is a later, strictly opt-in phase — gated by explicit config and never enabled implicitly.

What happens if I sell my machine? The agent identity transfers with the token — config, screen and history included. New wallet, same employee.