What authentication does the Clientary API use?

The API uses an API key in the Authorization header. Through Jentic, the key is stored encrypted in the vault and never enters the agent's context - the agent gets a scoped execution token instead.

Can I create invoices and estimates with the Clientary API?

Yes. POST /invoices creates an invoice and POST /estimates creates an estimate. Both accept line items, client id, and tax fields, so an agent can convert an accepted estimate into an invoice by reusing the same line-item payload.

How do I record a payment against an invoice with the Clientary API?

POST /payments with the invoice id, amount, and date. The endpoint links the payment to the invoice and updates its status. Through Jentic, search for 'record a payment in clientary' to load the schema and execute.

What are the rate limits for the Clientary API?

Clientary does not publish hard rate limits in the spec. Build clients to handle 429 responses with exponential backoff and check current limits with Clientary support for your account tier.

How do I generate an invoice from time entries through Jentic?

Run pip install jentic, then chain three calls: list /time-entries filtered by project and date, group by project, and POST /invoices with one line per project. Jentic returns each operation's input schema so the agent can build payloads without manual reference to docs.

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

Yes. Because you run Jentic One yourself, your own rules decide which Clientary operations and credentials the agent may use. You can allow read-only calls like GET /invoices and GET /clients/{id} while withholding write operations such as POST /invoices or PUT /invoices/{id}, so the agent never creates or edits records unless you add those operations. Since Clientary keeps resource ids in the URL path (/invoices/{id}, /clients/{id}), a rule can also pin the agent to a specific invoice or client.