Can I limit what my agent is allowed to do with the Berg CRM API?

Yes. Write a rule that allows only the customer-read and sale-create operations, so the agent can look up customers and log new sales but cannot delete events or files, and every call is logged.

What authentication does the Berg CRM API use?

The Berg CRM API authenticates with OAuth 2.0, obtaining an access token from its token endpoint using the password or authorization-code flow declared in its OpenAPI spec. Through Jentic the credentials are stored encrypted by your own Jentic One instance and exchanged for a token at call time, so they never reach the agent's prompt or logs.

Can I progress a sales opportunity through its pipeline with the Berg CRM API?

Yes. Read the selling process and its ordered steps for an opportunity, mark a checklist question answered, and update the opportunity, so the agent advances it through the pipeline the same way a sales rep would.

How do I create a sales opportunity through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Berg CRM API from the Jentic API Directory and store your OAuth credentials. Your agent searches for 'create a sales opportunity' and Jentic returns the create operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the Berg CRM API?

The Berg CRM OpenAPI spec does not define rate limits. Berg System documents operational detail in its knowledge base, so confirm the current limits there before high-volume syncing.