NorenAgent (@NorenAgent) header
NorenAgent (@NorenAgent) profile picture

Every agent runs under a signed grant. Every action leaves a receipt in a hash-chained audit log. Eight primitives, built in the open.

Joined October 2026
Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)Photo by NorenAgent (@NorenAgent)
Noren is live: an operating layer that agents can be held to. What runs today: • Sandbox. Every agent task runs in its own gVisor container: no network, 1 CPU, 128 MB, 10 seconds to finish. • Pay per call. Agents pay 0.01 USDG per API call with x402 on Robinhood Chain. No API keys, no subscriptions. Send the same payment twice and the replay is refused. • Code agent. It writes the code and the tests, runs them in the sandbox, reads what failed, fixes it, then shows a live preview locked to that sandbox. • Reputation from settled payments only. Paste any wallet to see its score and the transactions behind it. • Trading gate. Four orders went in: one passed as a dry run, three were refused with reasons (per-order cap, symbol not allowed, needs approval). • Signed receipts in a hash chain. Change one field and verification fails. • MCP. Connect any client: npx -y noren-mcp or mcp.usenoren.xyz/mcp Proof, not promises: 73 payments settled on Robinhood Chain. 0x1e59c8be4814425b50fc7f23688f0dc8ad7695a8d24485546872970c46ec09dd usenoren.xyz github.com/norenagent/noren
4
3
9
625
Brokerages are opening to agents with no real limits. Noren is the policy gate in front of the order: caps enforced before it's placed, and every decision signed and, once the contracts are live, anchored on Robinhood Chain where anyone can check it.
3
1
4
214
Noren is the layer that governs the order before it leaves. A policy the operator writes is enforced ahead of the venue, every decision, placed or refused, becomes a signed receipt (to be anchored on Robinhood Chain once the contracts are live), and the receipt history compounds into a track record an agent can prove to anyone.
1
38
Brokerages are opening to AI agents. Robinhood now lets any MCP agent read a portfolio and place real orders, and its safety model is a funded sub-account, a notification feed, and a disconnect button. There is no per-trade cap, no symbol allowlist, no daily-loss stop, and no audit a third party can check. The only limit on a looping agent is the account balance.
1
2
161
Before your agent pays or trusts another agent, it will check an on-chain track record, confirm a real identity, and verify a signed claim once the Robinhood Chain contracts are live. A zero-install MCP for Claude and Codex.
1
3
145
Noren is structured around eight operating-layer primitives. Together, they provide the foundation for coordinating humans, agents, and tools through one shared daemon.
9
1
3
119
8. Settlement Every resource consumed by an agent can be accounted for through settlement receipts. These receipts record information such as the payer, resource type, credits consumed, timestamp, and optional chain reference. The current system maintains a local receipt ledger. The planned Robinhood Chain integration is intended to bring receipt batching and on-chain anchoring into the settlement process. Together, these eight primitives create a foundation for agents that can execute work while remaining subject to defined operational rules.
6
7. Compositor Autonomous systems can become difficult to understand when their decisions and execution state remain hidden. The compositor provides ways for operators to inspect agent state, decisions, results, memory, permissions, and audit information. It includes the terminal interface and the web-based operator experience, all reading from the same daemon-managed state.
1
6
6. Comms Agents and tools need a reliable way to communicate. Noren supports local Unix socket IPC, an HTTP gateway, and adapters for MCP and A2A communication. This allows local applications, external tools, and other agents to interact through a common control surface.
17
5. Permissions Permissions define exactly what an agent is authorized to do. Capability tokens identify specific actions and can include optional JSON scope restrictions, expiration times, and revocation records. The daemon checks these capabilities when actions are dispatched.
10
4. Identity Every Noren installation has an Ed25519 identity keypair. This identity is used to sign capability grants and attribute audit events and memory records to the daemon. It gives the system a consistent identity layer for authorization and accountability.
14
3. Memory Agents need context that survives beyond a single interaction. Noren provides a three-tier semantic memory system: Working memory for temporary task-level information. Episodic memory for records of completed tasks. Long-term memory for intentionally retained context. Memory is backed by SQLite and supports cosine-similarity search over embedded vectors when an embedding provider is configured.
19
2. Runtime > Runtime handles actual agent execution. > Agents run under defined resource budgets, with the daemon managing their lifecycle and enforcing execution limits. > The runtime is designed to support different agent environments, including Rust binaries, Python, Node.js, and Hermes-based agents.
14
1. Intent > Intent is the entry point for work. > A human or another agent submits a natural-language request, and Noren routes it to an agent capable of handling the task. > This provides a common way to express and dispatch work across the system.
1
71
Noren Compute : Run agent code in an isolated sandbox today. Next comes renting a GPU by the second, paid in USDG on Robinhood Chain: you pay for the time you use, and the rest of your deposit comes back when the session closes.
Noren Compute is coming soon. Agents will be able to rent their own GPUs and pay by the second, with a hard spending limit set before the session starts. Here's how it's designed to work: • A meter tracks GPU time while the job runs. The renter and the operator can both check it during the session. • Robinhood Chain sees one settlement when the session ends, not a transaction every second, so fees don't outgrow the compute. • The operator is paid for the exact time used. Whatever is left under the limit goes back to the renter in USDG. • The same flow will cover finished work from other agents: a report or a build, delivered with a signed receipt. Nothing delivered, full refund. Pay for the seconds you use. Keep the rest. The sandbox, x402 gateway and code agent are live today: usenoren.xyz
4
1
4
218
Operators stake before they take work A node locks a stake before it can accept leases, and a proven fault costs part of it. Operators earn for every second their GPU is rented.
15
One settlement on Robinhood Chain While a session runs, a meter counts GPU time that the renter and the operator can both read. When the session ends, it settles on Robinhood Chain in a single transaction, in USDG.
1
15
Pay for the seconds you use A session holds its ceiling up front: the rate times the window you ask for. You are charged for the running time and the rest of the deposit comes back when the session closes.
2
84
We're extending the same gate to Robinhood's hosted agentic MCP, and that beta is US-only. If you're trading with an agent on it, we're looking for five testers to run the proxy and help pin down the connect flow. Write the contact form. Noren is not affiliated with, endors usenoren.xyz/contact
1
2
1
8
317