Let your AI handle the uploading.

Quick start

Three steps, about two minutes. You only do the first two once.

1. Create a key

   Open My account and find the API keys card. Name the key, tick only the permissions the job needs, and choose how long it lasts (30 days, 90 days or no expiry).

   Copy the key right away — it is shown once.

2. Hand it to your AI

   Store the key in an environment variable called FRAMEPEEK_API_KEY. Don’t paste it into a chat or commit it to a repository.

   Then give your AI the guide link and the starter message below.

3. Tell it what to do

   “Upload every JPG in ~/Trip into a new folder called Trip 2026.” Or: “Download everything in the folder Clients as a ZIP.”

   For many files the AI should write one loop, not one request by hand per file.

Manage the files in my framepeek account through its API.
First read https://framepeek.com/api-guide.txt completely and follow it exactly.
My API key is in the environment variable FRAMEPEEK_API_KEY. Never print it or write it to files or logs.
Start by calling whoami to check your permissions and free space. Delete only what I explicitly ask for.
Task: 

Prefer to run it yourself? Set up once per shell, then use fp in place of curl:

export FRAMEPEEK_API_KEY="fpk_…"   # paste your key here
B=https://framepeek.com
fp() { curl -sS -H "Authorization: Bearer $FRAMEPEEK_API_KEY" "$@"; }

fp $B/api/key/whoami

Command line

Prefer one command over a loop of requests? fp.mjs is a single file with no dependencies (Node 18 or newer). It uses the same API and the same key, so your AI can upload a whole folder in one go.

curl -fsSL -o fp.mjs https://framepeek.com/fp.mjs
export FRAMEPEEK_API_KEY="fpk_…"            # your key, from My account
node fp.mjs whoami
node fp.mjs upload ./Trip --folder "Trip 2026"
node fp.mjs download --folder "Trip 2026" -o trip.zip

If your AI cannot see the variable (some assistants keep secrets in a connector instead), fp stops with “FRAMEPEEK_API_KEY is not set” before contacting the server. In that case the assistant should make the same API calls through its connector, as described in the guide.

Permissions

Each key carries only the permissions you tick when you create it. Anything else is refused.

Endpoints

Base address https://framepeek.com. Send your key as Authorization: Bearer fpk_… on every request. Examples use the fp helper from the setup above.

Check your key read

List and download read

fp $B/api/items

T=$(fp -X POST -H 'Content-Type: application/json' \
    -d '{"ids":["<id1>","<id2>"]}' $B/api/download-zip \
    | sed -n 's/.*"token":"\([^"]*\)".*/\1/p')
curl -sS -o files.zip "$B/api/download-zip/$T"

Upload write

fp -X POST --data-binary @photo.jpg \
   "$B/api/upload?name=photo.jpg&w=1920&h=1080"
# {"ok":true,"item":{"id":"…","file":"…","name":"photo.jpg","w":1920,"h":1080,"size":12345,…}}

Upload one file at a time and collect the new ids. The AI guide has a ready-made fp_upload helper that reads image and video dimensions for you, plus a loop for whole folders.

Folders and moving files read · write · delete

Folders are one level deep (no folders inside folders), up to 200 per account.

fp -X POST -H 'Content-Type: application/json' -d '{"name":"Trip 2026"}' $B/api/folders

fp -X POST -H 'Content-Type: application/json' \
   -d '{"ids":["<itemId1>","<itemId2>"],"folderId":"<folderId>"}' $B/api/items/move

Delete and Trash read · write · delete

Files in the Trash still count toward your storage until you delete them for good in the web app or the 30 days pass. API keys cannot delete permanently or empty the Trash.

Share links share

Not available to API keys

Account settings, password, billing and plan changes, AI Restyle, saving someone else’s shared grid into your account, and managing API keys. Use the web app (Media Grid and My account) for those.

Errors

Errors come back as JSON with a status and a code. Match on the code.

Limits

These keep the service fast for everyone. They may change with the plans; whoami always shows your current numbers.

Safety

A key acts as your account. Treat it like a password.

• Keep it secret. Never put a key in a chat message, a screenshot, a URL, or a code repository. Use an environment variable or a secret manager.
• One key per job. Give each tool or script its own key with only the permissions it needs, and delete it when the job is done.
• Pick an expiry. A 30- or 90-day key limits the damage if it leaks.
• Confirm deletes. Have your AI show the list of files it is about to delete and wait for your yes. Deleting moves files to the Trash for 30 days, and a key cannot delete them permanently.
• Mind share links. A link is a public address. Check what is in it before you pass it on.
• If a key leaks, delete it in My account. It stops working at once. Resetting your password also deletes every key on the account.

Key requests are logged (time, kind of action, result, size) so abuse can be spotted. File names and the key itself are not logged. API use is covered by the API section of the Terms.