As work happens
Keep your app in the loop.
Use webhooks for supported events and check requests, keys, and usage in the developer console.
WebhooksFryri for developers
Give your app a library it can work with. Capture notes and files, retrieve what matters, and ask questions with sources.
Usage-based billing through your prepaid balance.
# Save a note for one user
curl https://api.fryri.com/v1/capture \
-H "Authorization: Bearer $FRYRI_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
curl "https://api.fryri.com/v1/search?q=Atlas&end_user_id=user_42" \
-H "Authorization: Bearer $FRYRI_KEY"CAPTURE → RECALL → BUILD ON IT
The building blocks
Start with one endpoint. Connect the pieces your product needs as you go.
Context with boundaries
Pass an end_user_id to scope supported calls to that user's library. Your account owns the keys and pays for usage.
user_01Own libraryuser_02Own libraryuser_03Own libraryAs work happens
Use webhooks for supported events and check requests, keys, and usage in the developer console.
WebhooksWhen you need more
Read documents as structured data, explore entity connections, and run research that your app can return to.
Explore the API referenceBuild something with context