Authenticated API
A documented API surface for connecting agent workflows.
IN REPOSITORYAGENT INFRASTRUCTURE / OPEN SOURCE
FROM INTENT
to action.
An execution layer for AI agents. Models can propose; controlled software defines what happens next.
AN OPEN-SOURCE PROJECT / CONCEPTUAL SYSTEM VIEW
INTENT↗POLICY↗APPROVAL↗SEPARATE SIGNERTHE EXECUTION BOUNDARY / 01
CONCEPT / NO LIVE DATA
01 THE ARCHITECTURE
INTELLIGENCE
meets boundaries.
An AI model can suggest an action. RetifyOS describes a runtime that places policy and controlled execution between that suggestion and the outside world.
The repository documents an untrusted planner, deterministic policy and execution controls, capability-scoped tools, approval workflows and a separate signer. These are documented design and code-path descriptions—not proof of a production deployment.
Read the architectureINTERACTIVE WALKTHROUGH / LOCAL DEMO
A clear line
before execution.
Follow a proposed action through a simulated check and an explicit operator decision. This is a visual explanation of a control boundary—not a live workflow.
Simulation only. This module uses local, illustrative data. It does not connect to an API, wallet, network or signer, and it cannot execute or approve a transaction.
BOUNDARY / 01
OFFLINE SIMULATION
- 01Proposal
- 02Check
- 03Approval
Intent arrives
as a proposal.
A model or another upstream process may suggest an action. Here, the proposal stays separate from execution.
- REQUEST
- Illustrative action
- ORIGIN
- Untrusted planner
- STATE
- Not submitted
Check the shape
before a decision.
The demo pauses to show where a deterministic check could inspect a proposal. No external system is contacted.
- INPUT
- Local proposal
- CHECK
- Illustrative only
- RESULT
- Reviewable
An operator
remains the gate.
The final card is a simulated approval checkpoint. Pressing the button does not authorize or submit anything outside this page.
- DECISION
- Simulated approval
- SIGNER
- Not connected
- NETWORK
- No broadcast
Nothing leaves this page. No API, wallet, network connection or transaction is involved.
02 A DOCUMENTED SOLANA / JUPITER PATH
ONE PATH.
Clear checkpoints.
The documented swap path makes the approval boundary explicit before signing and broadcast.
- 01Get a quotePrepare the proposed swap
- 02Simulate the exact transactionCheck the transaction before approval
- 03Operator approvalA distinct human checkpointAPPROVAL GATE
- 04Separate signerSigning is isolated from the planner
- 05Broadcast & reconcileFollow the result after submission
Important: live execution is disabled by default and requires explicit configuration and approval. The repository documents this path; this page does not claim a live transaction or production use.
Trading docs ↗03 DOCUMENTED INTERFACES
One project.
Several entry points.
Interfaces described in the repository. Their presence in source does not imply a live hosted service.
CLI
A command-line interface documented alongside the service.
IN REPOSITORYMCP
MCP-related interfaces for tool-connected agent workflows.
IN REPOSITORYTelegram ingress
An optional messaging adapter described in the project.
OPTIONAL ADAPTEROperator console
An operator-facing console. Without an API connection, it shows simulated data.
SIMULATION WITHOUT API04 FOR BUILDERS
Inspect the path.
Run it locally.
The operations guide documents a Node.js 22 setup and a local verification command. The README’s tests use offline fakes and local SQLite—useful for checking code paths, but not evidence of live-chain execution.
Open operations docsLOCAL / VERIFY
$ npm ci
$ npm run verify
NODE.JS 22OFFLINE TEST FAKES
05 NETWORK DIRECTION
Built with the boundary
in mind. Growing by design.
DOCUMENTED CODE PATH
Solana / Jupiter
A swap flow is documented from quote and simulation through approval, separate signing, broadcast and reconciliation.
Review the flowFUTURE TARGET · IN DEVELOPMENT
Robinhood Chain
A future target for the project—not a live integration.
ROADMAP / DEVELOPMENTMemory and skills are not wired into the main app. Drift, Meteora and pump.fun tools are not mounted in the default daemon and have no reported live tests. No production activity, transaction success, uptime, user counts, partnership or independent security audit is claimed here.
READ THE SOURCE
The next step is
in the repository.
Explore RetifyOS on GitHub
Code and documentation are the source for the architecture described on this page.