# Fryri

> Fryri is a personal AI that remembers what matters from your photos, documents, receipts and dates. The API lets your own apps and agents use that same brain: run full chat turns grounded in a library, capture new things, search and read documents as data, and run deep research. A key works on its own account's library by default, and any data call can instead carry `end_user_id` (an opaque string you choose) to act on a private per-user library under your key: first use creates it, `GET /v1/end-users` lists them, `DELETE /v1/end-users/{id}` erases one completely. Spend always lands on your account.

Base URL: `https://api.fryri.com`. Authenticate every request with `Authorization: Bearer fryri_sk_...` (create a key in the developer console at https://fryri.com/developers/console). All endpoints live under the `/v1` prefix. The docs pages below are each readable as markdown at their URL plus a .md suffix; the full corpus is at https://fryri.com/llms-full.txt.

## Help

- [Get things into Fryri](https://fryri.com/docs/help/getting-things-in.md): The ways to add files, photos, notes, emails and messages to your Fryri library.
- [Ask questions about your stuff](https://fryri.com/docs/help/asking-questions.md): How to ask Fryri about anything you have added, and how answers point back to sources.
- [What happens to your files](https://fryri.com/docs/help/what-happens-to-your-files.md): What Fryri does with a file after you add it, and where it stays.
- [Plans, usage and credits](https://fryri.com/docs/help/plans-and-limits.md): How the free plan, paid plans and credits fit together.
- [Delete things, or everything](https://fryri.com/docs/help/delete-your-data.md): How deleting single items and deleting your whole account works.

## Concepts

- [What Fryri is](https://fryri.com/docs/concepts/what-fryri-is.md): Fryri keeps what you give it, makes sense of it, and answers for it, so you can ask instead of dig.
- [Your library](https://fryri.com/docs/concepts/your-library.md): The library is everything you have given Fryri, organized for you and searchable by meaning.
- [Fryri comes to you](https://fryri.com/docs/concepts/proactive-surfacing.md): Fryri raises deadlines, renewals and loose ends on its own instead of waiting to be asked.

## Developer API

- [Authentication and keys](https://fryri.com/docs/api/authentication-and-keys.md): Create an API key and authenticate every request with a Bearer header.
- [Quickstart](https://fryri.com/docs/api/give-your-app-memory.md): Put something into memory and recall it, grounded with sources, in three calls.
- [Store and recall](https://fryri.com/docs/api/store-and-recall.md): Capture text or files into a library, then find them again by meaning.
- [Read documents as data](https://fryri.com/docs/api/read-documents-as-data.md): List documents, read their extracted text and typed fields, and map results back to your own files.

## API reference

- [OpenAPI spec](https://api.fryri.com/v1/openapi.json): the machine-readable contract for the whole `/v1` surface. Import it to generate a typed client, or hand it to an agent as the source of truth. Start here.
- [Interactive docs (Swagger UI)](https://api.fryri.com/v1/docs): browse and try every endpoint in the browser.
- [Human API reference](https://fryri.com/docs/api): the narrative version with a quickstart, authentication, and per-endpoint examples.

## SDKs

- [Python client (fryri.py)](https://fryri.com/sdk/fryri.py): a single-file HTTP client, no dependencies beyond the standard library plus one HTTP package. `from fryri import Fryri; c = Fryri("fryri_sk_...")`.
- [TypeScript client (fryri.ts)](https://fryri.com/sdk/fryri.ts): a single-file fetch-based client for Node and the browser.

## What the API does

The stable surface is five products; fast-moving beta endpoints live under `/v1/evolving`.

- Chat: `POST /v1/chat` runs a full chat turn grounded in your library, with sources. Supports streaming.
- Capture: `POST /v1/capture` and `POST /v1/capture/batch` add new material (text, files) so it becomes something the API can draw on later.
- Library reads: `GET /v1/search` (semantic search over your stuff), `GET /v1/grep` (literal pattern match), `GET /v1/documents` and `GET /v1/documents/{file_id}` (list and read your documents as data, with a download route), and `GET/POST/PATCH/DELETE /v1/facts` (the structured facts extracted from your library).
- End users: pass `end_user_id` on chat, capture, search, grep, graph, entities, facts, documents or library export to act on a per-user private library under your key; `GET /v1/end-users` lists them and `DELETE /v1/end-users/{id}` permanently erases one user's library.
- Research: `POST /v1/research` and `POST /v1/research/entity` kick off deep research jobs; poll `GET /v1/research/{job_id}` for the result.
- Billing and account: `GET /v1/usage`, `GET /v1/wallet`, and `GET/POST/DELETE /v1/byo-key` (bring your own provider key). These stay reachable even when a balance runs low, so you can always check state and top up.
- Beta (`/v1/evolving`): agent runs and user-defined skills. Interfaces under `/v1/evolving` may change without notice.