API reference
How APIs relate to PlutoAI: the apps you build, and the services PlutoAI connects to
This page explains where APIs fit in when you work with PlutoAI. There are two things people usually mean by "API," and PlutoAI relates to each one differently.
PlutoAI does not have a public API
PlutoAI does not currently offer a public API for controlling PlutoAI itself from outside the product. You build by talking to the agent in the app, not by calling an external endpoint. There are no API keys to generate for external access.
If a public API is something you need, let us know what you would use it for. It helps prioritize what to build.
The apps you build can have their own APIs
The apps you build with PlutoAI can expose their own APIs. If your project needs endpoints, for other software to read or write its data, ask the agent to build them, the same way you ask for any other feature. See Frontend and backend.
Add a REST API for the tasks in this app, with endpoints to list, create,
update, and delete a task. Require an API key on write requests.
PlutoAI connects to other services for you
When your project needs to work with an outside service, you do not wire up its API by hand. You connect the service with a secure sign-in, and the agent uses it inside your build. This is how connectors and MCP work. See Connect your tools and Using MCP integrations.