What authentication does the CupixWorks API use?

CupixWorks uses an HTTP bearer token in the Authorization header. Through Jentic the token is stored in your encrypted Jentic One instance and injected at request time so the agent never handles the raw secret in its prompt or outputs.

Can I publish an annotation layer with the CupixWorks API?

Yes. After creating a layer with POST /annotation-layers, run PUT /annotation-layers/{id}/publish to publish it to the wider team. Use the matching unpublish endpoint to revert if a reviewer flags an issue.

What are the rate limits for the CupixWorks API?

The Jentic-maintained spec does not publish explicit rate limits because CupixWorks does not document them publicly. Use modest batch sizes when bulk-creating annotation layers or progress entries and back off on 429 responses.

How do I create an annotation layer with the CupixWorks API through Jentic?

Run pip install jentic, search Jentic for 'create an annotation layer on a CupixWorks site', load the schema for POST /annotation-layers, and execute it with the site and metadata. Jentic injects the bearer token from your Jentic One instance so the integration code stays clean.

How do I track construction progress with the CupixWorks API?

Use the /progress endpoints to record progress entries against milestones. Pair them with the workflow and status endpoints to move milestones through the project's review states automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which CupixWorks operations and credentials the agent may use. Since the API puts the annotation layer id in the path (/annotation-layers/{id}), you can pin the agent to a single layer so it only reads and updates that one and nothing else. You also choose the operations it may call, so publishing or unpublishing a layer stays off limits unless you explicitly add it.