# Quickstart — OneDroid Synapse, Engram and the kits in ten minutes > Three things to try today: connect an agent to OneDroid Synapse, give it memory with OneDroid Engram, and run the open-source Dark Factory kits. Each ends with a check you can run yourself. Free for individuals and small teams. Canonical: https://onedroid.ai/quickstart OneDroid Quickstart # Three things to try today. Connect an agent to one governed endpoint. Give it memory that outlives the session. Run the open-source method the agent works under. Each takes about ten minutes, needs no credit card, and ends with a check you run yourself, so you never have to take our word for it. 1 · OneDroid Synapse ## Connect an agent to one governed URL. Synapse is a gateway between your agents and your accounts. Your agent connects once; every tool call is authenticated, policy-checked and written to an audit log you own. Free for individuals and small teams. 01 ### Create a hub Sign in at synapse.onedroid.ai with Google or an email code. Choose where your data lives — OneDroid Managed, or your own Postgres — and name the hub. It is yours; nobody provisions it for you. 02 ### Create a token In the hub, go to Manage → API Tokens → Create token. A token is bound to this hub and to you, and the plaintext is shown once, so copy it before you close the dialog. 03 ### Connect Claude Code One command, one header. Then `claude mcp list` should show `synapse … ✓ Connected`. `claude mcp add --transport http synapse \ https://synapse.onedroid.ai/agent/mcp \ --header "Authorization: Bearer "` ### Not in a terminal? Claude Desktop and claude.ai connect through a consent screen instead of a token. In the app, Settings → Connectors, add a custom connector with `https://synapse.onedroid.ai/hub//mcp`. Your hub's AI Clients page prints the exact URL for you. The browser route. ### The step that catches everyone Enabling a service on your hub and saving your login for it are two different actions, and only the second lets an agent call anything. If the agent connects and then sees no tools, this is why. Connections and credentials. ### The check Run this before you wire anything else. A good token returns HTTP 200 with a JSON-RPC result; a wrong one returns `401 invalid_token`; a missing header returns `401 missing_token`. Three different answers, so you always know which half is wrong. `curl -s https://synapse.onedroid.ai/agent/mcp \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize", "params":{"protocolVersion":"2025-06-18", "capabilities":{}, "clientInfo":{"name":"probe","version":"1.0"}}}'` Watch it done: the Synapse walkthrough, recorded against the live service, at youtu.be/WJvsBV4sXFU. Full walkthrough with screenshots: Set up your hub → Connect Claude Code → Connections and credentials. Every call on those pages was run against the live service. 2 · OneDroid Engram ## Give your agents memory that outlives the session. Engram is versioned, permissioned context in a Postgres you control, searched by vector, keyword and graph at once, and reachable by any MCP client behind any model. It is included with a Synapse account and runs on its own. 01 ### Get a library token Sign in at engram.onedroid.ai, open API Tokens, and create a library token. It reaches one library and nothing else, which is the right default for an agent, a teammate or a pipeline. 02 ### Point a client at it Any MCP client that speaks streamable HTTP and can send a header. Or reach it through your Synapse hub, where the Engram connection is already on and every call is audited with the rest of your tools. `https://engram.onedroid.ai/mcp Authorization: Bearer ` 03 ### Write one thing, search it back Ask your agent to write a note into a namespace with `engram_write`, then find it with `engram_search`. The write returns an object id; the search returns that object. That round trip is the whole idea: what one agent wrote, the next one can find. ### The check Send the same `initialize` probe as above to `https://engram.onedroid.ai/mcp` with your Engram token. A good token gets HTTP 200 and a server named `engram`; no token, a wrong one or a revoked one gets HTTP 401 with a plain-text `Unauthorized`. ### Your own database Point Engram at your own Postgres and documents, chunks, embeddings and history are rows there, readable with SQL. It needs the pgvector extension, which Engram enables at registration; Postgres 16 is what we test against. ### Every write is a commit Objects carry revision history. Diff any two versions, restore a previous one in one call. An agent that overwrote something important is a one-call fix, not a loss. Watch it done: the Engram walkthrough, recorded against the live service, at youtu.be/1o5mPIGCngk. The full path, with every call and response shown: Using Engram. Prefer a browser? The Engram web app does most of it by hand. 3 · The Dark Factory kits ## Run your agent under a method you can audit. The kits are the method OneDroid Argus enforces, written down as skills, hooks and gates any capable agent harness can run. Open source, Apache-2.0, no paid tier. Agents do the work; evidence, not self-reports, decides what ships. 01 ### Clone and list the kits The repository is github.com/OneDro1d/dark-factory (public, Apache-2.0). Seven kits today: `method-core` (the method itself), `dev`, `knowledge-worker`, `agent-ops`, `code-review`, `distributed-systems`, `frontend`. `git clone https://github.com/OneDro1d/dark-factory cd dark-factory bash starter-kit/instance/bootstrap.sh --kit list` 02 ### Make your own copy The bootstrap writes a new directory beside the checkout, pinned to the method at today's commit. Open Claude Code there and tell it: "Read START-HERE.md and execute it." It installs the skills, hooks and gates, and stops only where a human decision is needed. `bash starter-kit/instance/bootstrap.sh my-agent --kit dev cd ../my-agent` 03 ### No skill system? One page For ChatGPT, Gemini or a plain API model, paste DARK-FACTORY-PRIMING.md into the conversation. It inlines the whole method — every stage skill and the adversary gate — so the agent needs nothing else. ### The check The runbook ends with a validation run that commits its own report into your copy. If the report is not in the repo, the setup is not done, whatever the agent says. That rule is the method in one sentence. ### What you get Stage skills for product owner, architect, test-first developer and QA; an adversary gate that checks evidence without redoing the work; dispatch patterns for parallel sub-agents; an autonomy policy for what stops for a human. ### Where it leads The kits are what the gate checks against. OneDroid Argus is the gate: acceptance scenarios the agent never saw, run against the exact build, with a verdict you can replay. Early access, and the page says so. Read the method first if you like: the kits page and the repository. ## Something did not work? Troubleshooting michal@onedroid.ai The troubleshooting page covers the failures people actually hit, with the one probe that tells them apart. The address reaches the people who build the product.