Skip to content

Fryri for developers

Your app.
Their context.
Connected.

Give your app a library it can work with. Add files and notes, retrieve what matters, and ask questions with sources.

Usage-based billing through your prepaid balance.

# Add a memory for one of your users
curl https://api.fryri.com/v1/memories \
  -H "Authorization: Bearer $FRYRI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Project Atlas uses Python and FastAPI.",
    "title": "Project notes",
    "end_user_id": "user_42"
  }'

# Find it again, usually searchable within seconds
curl https://api.fryri.com/v1/search \
  -H "Authorization: Bearer $FRYRI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "What does Atlas run on?",
    "end_user_id": "user_42"
  }'

ADD → SEARCH → ANSWER

The building blocks

Less plumbing.
More product.

Start with one endpoint. Connect the pieces your product needs as you go.

Context with boundaries

A library for
each of your users.

Pass an end_user_id to scope any call to that user's library. Your account owns the keys and pays for usage.

Read about user scoping
Your application API KEY
user_01Own library
user_02Own library
user_03Own library

As work happens

See what your app sends.

Each memory reports its status, so your app knows when search can find it. The developer console shows every request with its status, timing and cost, next to your keys, spend caps and usage.

Request log

When you need more

Go beyond a saved note.

PDFs, Word, PowerPoint and Excel files, Markdown and source code are memories too. Search results point to the matching lines in a document, and answers return cited source lines and conversation turns.

Explore the API reference

Build something with context

Your first call is a good start.

Open the console