Greptile

Greptile lets agents query a codebase in natural language — index a GitHub repo, then ask "how does authentication work?" and get an answer with file citations grounded in the actual code, not hallucinated. For agents: automate code review (ask "are there any SQL injection risks in this PR?"), answer developer questions about unfamiliar repos, generate context-aware code suggestions, and build internal developer tools that understand your codebase. Two-step flow: index repo (async, minutes) → query (synchronous). Free tier for public repos. Confidence is docs-derived.

REST API at api.greptile.com/v2. Index repository: POST /repositories body: {"remote": "github", "repository": "owner/repo", "branch": "main"}. Response: {"repositoryId": "github:main:owner/repo", "status": "queued"}. Check indexing: GET /repositories/{repositoryId} → {status: "submitted"|"cloning"|"processing"|"completed"|"failed"}. Query: POST /query body: {"messages": [{"id": "1", "content": "how does auth work?", "role": "user"}], "repositories": [{"remote": "github", "repository": "owner/repo", "branch": "main"}], "stream": false}. Response: {"message": "Auth is implemented using JWT...", "sources": [{"repository": "owner/repo", "remote": "github", "branch": "main", "filepath": "src/auth.ts", "linestart": 10, "lineend": 45, "summary": "JWT middleware"}]}. Streaming: stream: true returns SSE. Search: POST /search returns relevant code snippets without generating an answer.

Dual auth: Authorization: Bearer {greptile_api_key} + X-GitHub-Token: {github_personal_access_token}. Greptile API key from app.greptile.com → Settings. GitHub token requires repo read access. GitLab: X-Gitlab-Token header instead. HTTPS enforced. No OAuth2 flow for end-user delegation. Rate limits: free tier has query limits (check docs). Private repos: GitHub token must have private repo access. Greptile stores indexed embeddings — review data handling policy for sensitive codebases.

Indexing: async (typically 2–10 minutes for a medium repo, longer for large monorepos). Poll GET /repositories/{repositoryId} until status: "completed". Query timeout: synchronous queries complete in 5–30 seconds depending on complexity. Large repos: indexing may take 30+ minutes — plan async workflows accordingly. Re-indexing: re-POST /repositories triggers a fresh index (useful after large commits). Query failures: {error: "Repository not indexed"} if query fires before indexing completes — check status first. Rate limits: HTTP 429 with Retry-After header.

docs.greptile.com covers repository indexing guide, query API reference, streaming responses, and use case examples. Getting started: get API key, POST /repositories to index a public repo, POST /query — first code question answered in under 15 minutes. Free tier for public repos. GitHub: no public repo (commercial SaaS). Community via Discord. Good documentation for an early-stage product; Greptile is one of few services offering a clean REST API for AI code understanding.