Carbon Inc Carbon REST API

What authentication does the Carbon REST API use?

Carbon uses HTTP bearer authentication with a JWT. Call POST /register to obtain a token, then send it in the Authorization header as `Bearer <jwt>` on every subsequent request. Through Jentic the JWT is held in the encrypted credential vault and rotated automatically, so agents never see the raw token.

Can I queue a 3D print job through the Carbon REST API?

Yes. POST /prints submits a new print job referencing a partId and a target printerId. The response returns the print job identifier, which you can poll with GET /prints/{printId} to track status from queued through completion.

How do I list all printers in our Carbon fleet?

Call GET /printers to retrieve every printer registered to the account, including its status. For details on a single unit, call GET /printers/{printerId} with the printer's ID. The /printers endpoints are read-only - provisioning and configuration happen in the Carbon dashboard.

What are the rate limits for the Carbon REST API?

The OpenAPI specification does not declare explicit rate limits. Limits are enforced by Carbon's gateway based on your account tier; if you hit a 429 response, slow polling on /prints/{printId} or batch reads where possible. Contact Carbon support for the quota tied to your account.

How do I create a print job with the Carbon REST API through Jentic?

Run `pip install jentic`, then use Jentic's search to find the print-creation operation with the query "create a 3d print job", load its schema, and execute with `{"partId": "PART-123", "printerId": "PR-01"}`. Jentic calls POST /prints, attaches the JWT from the vault, and returns the new printId.

Does the API let me upload new part designs?

No. The /parts endpoints only read the existing parts library - GET /parts to list and GET /parts/{partId} to fetch a specific record. Part design upload happens through Carbon's design tooling and dashboard, not this REST surface.

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

Yes. Because you run Jentic One yourself, your own rules decide which Carbon operations and credentials the agent may use. You can allow only read operations such as GET /printers and GET /printers/{printerId}, and since the printer ID sits in the URL path you can pin the agent to a single printer for status reads. Print job creation via POST /prints stays off limits unless you explicitly add it.