Connect your own agents

Start in the terminal

curl --fail https://namastesuite.com/namastesuite-cli.py -o namastesuite-cli.py
python3 namastesuite-cli.py login --email you@example.com --workspace your-workspace
python3 namastesuite-cli.py tools
python3 namastesuite-cli.py session --title 'Marketing work'

The client uses Python 3.9 or later and the standard library. It prompts privately for your password, stores session tokens with private file permissions, and refreshes them before work. Use separate credential files for separate accounts.

Discover, prepare, approve

Use the returned conversation ID for related work. Each tool declares its required role, workspace module, JSON arguments, and confirmation requirement. A proposed change returns the exact stored action for review. Confirming consumes that action once; do not retry a mutation after a timeout.

python3 namastesuite-cli.py call list_leads --session "$SESSION" --json '{}'
python3 namastesuite-cli.py confirm "$PENDING_ID" --session "$SESSION" --approve
python3 namastesuite-cli.py logout

HTTP API

Base URL: /api/v1/agent/. POST JSON to auth with grant_type: password, email, password, and workspace (slug or UUID). Refresh with grant_type: refresh_token, refresh_token, and workspace.

Authenticated requests require Authorization: Bearer <user-access-token> and X-NS-Workspace: <workspace-uuid>. GET tools returns the live catalog. POST sessions with a title; POST call with conversationId, tool, and arguments. POST confirm with conversationId, pendingId, and approved: true, or POST cancel with the same IDs. POST logout revokes the presented login session.

Check the tool's success and confirmationRequired fields, not only HTTP status. Requests are limited to 128 KiB. Authentication is limited to 10 requests per IP per minute; authenticated use is limited to 60 requests per user per minute and 120 per IP per minute.

Access follows your workspace permissions

Membership, plan, modules and roles are checked on each request. Business actions retain row-level security and their existing audit, consent, suppression, provider and quota checks. The workspace's AI Studio switch disables tool access. Deterministic calls do not require an internal chat model; individual AI tools keep their provider requirements.

Capabilities cover registered CRM, email/SMS, social, ads, analytics and tracking-site operations. Workspace owners can also manage brand-agent profiles and controls. Database access, platform administration, billing changes, provider secrets and unlisted dashboard settings are not exposed. Connecting an external account still requires its normal authorization flow.

User access tokens retain the user's normal workspace memberships. Give an automation account membership only where it should work. Store tokens privately and share with an external agent only the access and data you intend it to receive. Existing ingestion API keys do not authenticate this API.

Repository knowledge sources require separately authorized access. Editing an agent's source list does not grant access to another workspace's private repositories or shared credentials.