About Marrow
Marrow is a private, source-backed knowledge layer for professional work. You start in the console, add source material, then query the evidence Marrow distilled from it.
The public surface is intentionally small: account setup, API keys, CLI configuration, URL/file ingest, ingest status, evidence-backed query, and usage monitoring.
Key Capabilities
- Console-first setup: Create an account, review usage, and copy a one-time API key for the CLI.
- URL and file ingest: Queue public URLs or local files for source-backed distillation.
- Ingest status: Check recent jobs and individual job status from the CLI.
- Evidence-backed query: Ask a natural-language question and receive a compact answer with source excerpts.
- Usage guardrails: Query and ingest consume Marrow credits so account usage stays bounded.
- API key basics: List keys, create a replacement, and revoke old keys.
Tool Selection
| I want to... | Use |
|---|---|
| Sign up, get a key, or check usage | Console |
| Configure my local CLI once | marrow api configure |
| Preview or queue a URL ingest | marrow api ingest-url |
| Preview or queue a file ingest | marrow api ingest-file |
| Check recent ingest jobs | marrow api ingest-jobs |
| Check one ingest job | marrow api ingest-job |
| Ask for source-backed evidence | marrow api query |
| Manage my API keys | marrow api api-keys |
Boundaries
- Not a resume builder. Resumes are outputs. Marrow keeps the underlying source context reusable across downstream tools.
- Not generic chat memory. Every returned record carries source and confidence context.
- Not a public lookup database. Each account is private and API-key gated.
- Not a broad toolkit yet. The public path is deliberately limited to account setup, keys, ingest, status, query, and usage.
Get Started
- Quickstart: The same path in the shortest command form.
- Marrow CLI: Hosted CLI install, configure, ingest, status, query, and API key basics.
- Usage and credits: Check balances, understand credit costs, and read usage headers.
- API reference: Direct HTTP details only when you are building an integration instead of using the console and CLI.