REST API with OpenAPI 3
On api.photopilot.ai, with an OpenAPI 3 specification. For studio and camera, shoots, uploads and downloads. A webhook lets your own system know when something has been published.
https://api.photopilot.ai/A public API following the OpenAPI standard for your own software, and an MCP server that lets Claude and other AI assistants work in Photopilot with your rights.

An API or MCP server connects systems, but does not free you from one vendor. Open Brand Exchange does: an open agreement on how brands deliver product data and images to retailers. The format is open, your data is not.
Photopilot speaks the languages other software speaks too, from API and MCP to product feed and FTP.
The open agreement for product data and images between brand and retailer. The brand decides who gets access.
Model Context Protocol: the open standard that lets an AI assistant work safely with other software.
A public description of the API, so every developer knows what they can call.
Sign-in with consent: you give an app access without giving away your password.
Product feeds in common file formats that almost any system can create and read.
Files in a folder on your own server, with your own file names.
MCP is an open standard that lets an AI assistant, such as Claude, talk to other software. Photopilot has its own MCP server: your assistant looks up items, checks settings and changes things, with your rights.
The assistant works as the user who connects it, with exactly their rights. What you can't do, it can't do either.
Search items, view image positions and barcodes, settings, active connections and failed imports.
Every change is strictly checked beforehand and logged afterwards. Accounts, access and API keys stay with people.
Per connection at most 120 calls and 30 changes a minute.
Under My account → AI assistants. Access stops immediately.
The connection address is the same for every assistant. You sign in to Photopilot and click Allow; your password never reaches the assistant. OAuth 2.1 with PKCE and automatic registration of the assistant takes care of that.
https://app.photopilot.ai/mcpclaude mcp add --transport http photopilot https://app.photopilot.ai/mcpnpx mcp-remote https://app.photopilot.ai/mcpAn API is the entrance through which your developers' software talks directly to Photopilot, without anyone copying things over by hand.
On api.photopilot.ai, with an OpenAPI 3 specification. For studio and camera, shoots, uploads and downloads. A webhook lets your own system know when something has been published.
https://api.photopilot.ai/The Photopilot app itself runs on a GraphQL API. A connected assistant can use it through the MCP server: reading with your rights, and changing after the same strict checks.
You're not tied to anything.
You pay nothing to get started.
Download in your own formats, or everything at once as a zip.
Built by our own, 100% Dutch development team.
Flip the switch
Enter your web shop and flip the switch. You'll see how much of your range we get online automatically, with a price estimate and a plan.