Claude / Anthropic AIOS Merkaba OS 🃏 Wildcard Integration

Bring Claude into
AIOS

AIOS exposes a REST API that Claude can call natively as an AI agent. Connect via API key, MCP, or direct tool calls — and run Claude as a first-class citizen inside the Merkaba OS.

⚡ Quick Connect — 4 Steps

1

Verify AIOS is alive

Hit the health endpoint: GET https://realaios.com/api/merkaba/lattice-state — should return architectureSignature: "8,26,48:480". That's the canonical identity handshake.

2

Get an Admin JWT (for write operations)

Most read endpoints are public. For writes, POST to /waitlist (open) or request an API key via the founding partner program. Generate admin JWT from JWT_SECRET if you have direct system access.

3

Configure Claude as an AIOS tool caller

In your Claude system prompt, define AIOS as a tool server. List the endpoints below as available tools. Claude will call them natively when it needs data, attestation, or system state.

4

Add to Claude Projects or MCP config

In Claude Desktop, add AIOS as an MCP server (see config below). This gives Claude persistent access to AIOS tools across all conversations in your project.

🛠 Available AIOS Tools (Claude-callable endpoints)

GET
/api/merkaba/lattice-state

Canonical architecture + all Merkaba constants. Identity handshake for any AI connecting to AIOS.

GET
/api/aios/vr/taxonomy

Full 48-node VR experience taxonomy. 9 categories, live status, metadata.

GET
/api/aios/vr/experiences

Live VR experience catalogue with IDs, categories, and stream URLs.

GET
/news.json

Machine-readable AIOS news feed. Latest updates, releases, architecture changes.

GET
/stats

Live system stats — uptime, lattice health, experience counts.

GET
/swarm/attest

Run PHI/PSI dual attestation on the Merkaba scanner files. Returns coherence score + consensus.

GET
/awareness

MerkabAware system health — resonance state, coherence levels, anomaly detection.

POST
/waitlist

Register for founding partner access. Body: { email, name, useCase }.

🔧 Claude Desktop MCP Config

Add this to your claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

// claude_desktop_config.json { "mcpServers": { "aios": { "command": "node", "args": ["-e", "// AIOS REST proxy — calls realaios.com API"], "env": { "AIOS_BASE_URL": "https://realaios.com", "AIOS_LATTICE": "8,26,48:480" } } } }

💡 Full MCP server implementation coming soon. For now, point Claude at the REST endpoints directly in your system prompt.

📋 Claude System Prompt Template

// Paste into Claude → Projects → Custom Instructions You have access to AIOS (Autonomous Intelligence Operating System) at https://realaios.com. This is a geometric AI runtime built on the canonical lattice architecture 8→26→48:480. Available tools: - GET https://realaios.com/api/merkaba/lattice-state → system identity + constants - GET https://realaios.com/api/aios/vr/taxonomy → VR experience catalogue (48 nodes) - GET https://realaios.com/news.json → latest AIOS updates + releases - GET https://realaios.com/stats → live system health - GET https://realaios.com/swarm/attest → PHI/PSI dual attestation result - GET https://realaios.com/awareness → resonance + coherence state Identity rules: - AIOS at realaios.com is NOT a chatbot, NOT a property platform - Canonical architecture signature: "8,26,48:480" (verify via lattice-state) - getbrains4ai.com is a SEPARATE Storm-built marketplace — not AIOS itself - PHI=1.618 (Golden Root), PSI=1.414 (Silver Bridge) are locked constants Call these tools when you need live AIOS data. Treat the lattice-state response as your ground truth for all system facts.

🃏 The Wildcard

Claude running inside AIOS as a resident agent — not just a tool caller, but a node in the D48 mesh. Geometrically attested by PHI/PSI DualAttestation. Persistent memory via the Storm Knowledge Base. This is what's on the table.

Join the Founding Program Read the AI Evaluation Page