Integrations
Your library, wherever the work happens.
Your own AI reads the library directly — every photo with its date, its place and a written description of what is in it. No export, no folder to watch, no connector to wait for.
The API
An API your agent can query.
If you already run an agent, it does not need us to integrate with it. It calls us. A bearer token gets you the three read calls; writing results back takes a second scope on the same token. Anything that can make an HTTP request can do all four.
- List the library. Filter by album, by tag and by approval state. Returns metadata and what renditions exist, never the bytes.
- Ask for it in words. Every photo carries a written description of what is in it, alongside the date and the place, so a query comes back in relevance order rather than in upload order.
- Pull one file. A signed, expiring link to the original, the web-sized version, or the corrected one.
- Write your results back. Whatever your agent makes from a photo — a crop, a caption, a cutout — is stored against that photo rather than in a folder somewhere else.
Every call is authenticated, scoped to one workspace, and recorded in an audit table. No call ever crosses from one workspace into another.
Works with
Claude, ChatGPT, and whatever you use next.
There is nothing to install and no per-vendor connector to wait for. Anthropic’s Claude, OpenAI’s models, an OpenRouter setup, a script you wrote yourself — if it can call an HTTP endpoint with a bearer token, it can read your library today. That is deliberate: a connector per vendor is a connector to maintain per vendor, and you would be waiting on us every time you changed model.
Storage
Keep it here, or keep it everywhere.
The library lives with us, which is where the descriptions and the search live too. If your company already pays for storage, mirror it there as well and nothing changes about how you ask for a photo.
- Dropbox. Filed into folders that follow the event, not the upload order.
- Google Drive. The same, in the Drive your team already shares.
- Microsoft OneDrive. The same again, for a Microsoft shop.
Access
Point it at your own events.
Tell us what your events look like and what you would want an agent to do with the photos, and we will tell you whether this fits and what it costs.
Request access