This walkthrough checks that your assistant is connected to the right account and can inspect the intended project. It needs an API key with projects:read and a completed client setup.
Check your account
Start a new conversation with Agiler enabled and ask:
Use Agiler’s whoami tool. Tell me which account is connected and which effective scopes the key has. Do not make changes or display credentials.
Check the returned identity against your Agiler account. A successful whoami call verifies authentication, but does not by itself verify access to a particular project.
Find the right project
Ask:
List the Agiler projects I can access. Show their names, identifiers, and status. Follow pagination if there are more results. Do not create or modify anything.
The assistant should use projects_list. Choose the intended project and use the returned identifier in later prompts. If the project is missing, review the key’s resource restrictions and your workspace membership.
Inspect the configuration
Replace <project-id> with the identifier you selected:
For Agiler project
<project-id>, inspect its project settings, connected domains, and backup policy. Summarize what you find, including whether the project is ready. Use read tools only and do not change anything.
The relevant tools are projects_get, domains_list, and backups_get_policy. Compare the summary with the dashboard. If the project is provisioning or in maintenance, wait for it to become ready before attempting file or database work.
Check the result
You should now have the connected account, the exact project identifier, and a summary backed by tool results. If the assistant could not call a tool, ask it to report the error rather than infer the answer.
If authentication succeeds but tools or projects are missing, follow troubleshooting. Once the inspection works, try an example workflow. Add write or execution scopes only when a task needs them.