- “Show me the tables in my project and what’s in
orders.” - “Add a
notesfield tocustomers.” - “Why did the last three runs of the
welcome-emailflow fail?” - “Create a flow that emails the team when an order is paid.”
Connect a tool
Open AI → AI tools in Studio. It walks through three steps:1
Give it a key
Choose how much the tool may do:
The key is shown once. Copy it now.
2
Add Pawabase to your AI tool
Studio shows the exact setting for your tool, with your address filled in. For Claude Code it is one line:Cursor, Codex, Copilot and any MCP client take the same address and an
apikey header.3
See what it did
Every call the tool makes is listed under AI → AI tools, with what it asked for and when.
What it can see and do
The tool is given only the actions its key allows, and it cannot get past that. Start with Look only, and move to Build with me when you want it to make changes. Keep keys for secrets, users and other keys out of AI tools. It can work across the parts of your project: data, access rules, flows, routes, storage, mail, webhooks, schedules, monitoring and usage. It also comes with ready-made prompts for common jobs, such as designing a table or investigating a failing flow.Treat an AI tool like a new teammate: give it a key that matches what you want it to do, ask it to explain before it changes something important, and review what it did in AI → AI tools.
Safety
- Scoped keys. The tool can only do what its key allows. This is the hard limit.
- It asks first. Anything permanent, such as deleting a table or sending an email, is held until you confirm in your tool.
- It leaves a record. Each call is listed, with the names of what it asked for. Values such as secrets are never recorded.
- Revoke any time. Delete the key under Settings → API keys and the tool stops working at once.