Repo is a context layer for agents. Connect your team’s Slack, Notion, Drive, and Gmail. Repo ingests them, governs access by scope, and serves cited answers to your agents through a single API.Documentation Index
Fetch the complete documentation index at: https://docs.userepo.com/llms.txt
Use this file to discover all available pages before exploring further.
What you get
- Source-backed answers. Every
/v1/askresponse includes citations to the original Slack message, Notion page, Drive file, or Gmail thread. No black-box generation. - Scoped API keys. Each agent gets its own key with per-action and per-provider scopes — a customer-support agent can read Slack but not Gmail; a sales agent can read Drive but not write back.
- Freshness + audit. Every sync run, every retrieval, every key creation, every connector change is logged. Your security team can answer “what did the agent see?” the same way they answer “what did the user see?”
- One config layer for context. OAuth, chunking, embeddings, freshness windows, citation formatting, scoped retrieval — Repo owns it. You ship agents.
Who Repo is for
Technical teams shipping production agents who need governed company context through an API. Specifically:- AI automation agencies building Slack/Drive-grounded agents for SMB and mid-market clients
- AI-native B2B SaaS companies integrating Repo as the context layer behind their product
- Internal platform teams at 50–500 person companies standing up their first production agents
Architecture at a glance
Console
Where humans connect sources, mint API keys, and watch sync health.
API
Where your agents retrieve context, ask questions, and stream cited answers.
Worker
Background sync that keeps Repo’s memory fresh — runs every 15 minutes by default.
Audit
Every retrieval, key, and connector change is logged with metadata-only redaction.
Next steps
Quickstart
Sign up, connect Slack, mint a key, and get your first cited answer in under 5 minutes.