THE CONNECTION FLOW
Three steps.
Then get back to work.
Your email code signs you in. You approve each agent connection separately and can revoke it later.
Open your workspace
An eight-digit email code opens your account. Your allowance belongs to you and is shared across your agents.
Connect your agent
Add the engine URL in an agent that supports remote MCP. Review the connection and approve the services it may use.
Ask a dependent question
Have your agent use sysone_code to find relevant evidence, branch on the result and check only what matters. Inspect its answer and usage in your workspace.
Checking a file? Grant temporary document access to that connection separately. Upload bytes through its one-use HTTP URL, then let Code Mode search short excerpts by document ID. Documents become inaccessible after 12 hours. See the file workflow →
FREE EARLY ACCESS
Free Jev access for verified accounts
Use the hosted playground, MCP or API from one verified account.
- Daily usage limits apply across all free accounts
- One Jev allowance shared across playground, MCP and API
- Hosted Code Mode has a separate daily execution limit
- Up to 1 GiB of decision input per UTC day
- No provider key, payment card or waitlist required
- No automatic upgrade or paid overage
Each Jev attempt counts against free access. Failed calls and calls without reported usage may still count. Daily capacity, request size and rate limits apply. Free access renews at 00:00 UTC.
Add this remote MCP endpoint
https://cloud.systemoneengine.com/mcpVerify your email first, then add this URL in your agent. Complete the connection approval in your signed-in browser. Then try sysone_code for a dependent plan or a direct tool for one check. See the Code Mode example and limits. Read the hosted setup guide → For an application, create a scoped API key in your workspace and use the SDK or HTTP API. Both share your daily allowance with the playground.
Inspect each decision and its usage.
The workspace records the connection, response time and reported usage for each request. A coding task evaluation found no improvement on nine small tasks; prompted calls took longer. Use Jev when a bounded check can change the next step.
Prefer to run it yourself?
The local preview remains available with npx sysone. Use your own Vercel AI Gateway key, keep your engine on your machine and pay your provider directly.
Which agents work?
The engine uses remote HTTP MCP and explicit authorization. Choose the setup for your agent. Individual agents differ in their remote connection and authentication support. We have verified the hosted OAuth flow and remote MCP with the protocol SDK. Native ChatGPT, Claude Code and Cursor cloud setup reviews are still pending. Current local and remote setup guidance →