Docs
For people, and for the agents helping them.
Every page here is also fetchable as plain markdown at the same path with /raw appended (or ending in .md), with no sign-in and no API key. See /llms.txt for the machine-readable index, or /llms-full.txt for the whole corpus in one fetch.
Start here
- New here, no GPU and no invitation: Quickstart
- Connecting an app: Use your Circle from anywhere
- Have a GPU to share: Hosting your GPU
- Deciding whether to trust it: Privacy and egress
Start
New here. Install, and understand what you are joining.
- Quickstart
Install the CLI, ask your first question, and recover when a step fails.
New member
- Concepts
Circle, Host, Guest, Pool, receipts, and why consumption is on by default.
New member · Evaluating Saylek · Members
Use
Running your Circle day to day.
- Circles and membership
Joining, creating, and leaving a Circle, and who is actually able to get in.
Members · New member · Evaluating Saylek
- Invite flow
Email an invite to one person, and manage the invites you have sent.
Members
Integrate
Point an app, an SDK, or a coding agent at your Circle.
- Connect your app
Point an existing OpenAI-compatible client at your local daemon.
Developers
- Use your Circle from anywhere
Point an OpenAI-compatible client at the hosted endpoint with a member API key.
Developers
- Claude Code & the Anthropic SDK
Point Claude Code and the Anthropic SDK at your Circle.
Developers
Operate
Contribute capacity, and fix things when they misbehave.
- Hosting your GPU
Contribute capacity to your Circle, and the three different ways to stop.
Hosts · Members
- Troubleshooting
Symptoms, what the state actually is, and how to get out of it.
Members · New member · Developers · Hosts
Trust
What leaves your machine, and what we do not claim.
- Privacy and egress
What leaves your machine when a Circle-mate serves you, and the two ways to stop it.
Evaluating Saylek · Members · Developers
Reference
Generated tables and the command surface.
- API reference
Base URLs, supported endpoints, streaming, model ids, and how failure looks.
Developers
- Common commands
The everyday command table and the leaving/pause/delete options, generated from README.md.
Members · New member
Terms, privacy, and security
- Evaluate Saylek: The unauthenticated technical-evaluation surface: architecture and trust boundaries, supported platforms, the API surface, what provenance can be checked, and what does not work yet.
- Terms of Service: The beta terms, including the Circle-egress disclosure: a request your device cannot serve runs on another member's GPU.
- Acceptable Use Policy: What may and may not be run on the pool, what running `saylek host wizard` commits a Host to, and who is answerable for what.
- Privacy: What information Saylek handles, including prompts and completions, and what is retained.
- Security: Signed receipts, email-blind identity, passwordless sign-in, and how to report a vulnerability.