Carbon Inc Carbon REST API
70
AI ReadinessAI-Aware (B+)70/100
Agent-ready OpenAPI document · curated by JenticIOTDevice Managementbearer8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Queue and monitor 3D print jobs on a Carbon printer fleet, list connected printers, and look up parts in the manufacturing library.
Use for: I need to start a print job on an available Carbon printer, List all printers in our manufacturing fleet and their current status, Check whether print job 12345 has finished, Find a part by ID before queueing a new print
Not supported: Does not handle CAD design, slicing, or part upload - use for printer fleet status, print job orchestration, and parts lookup only.
Jentic publishes the only available OpenAPI specification for Carbon REST API, keeping it validated and agent-ready. The Carbon REST API automates Carbon's industrial 3D printing workflow, exposing JWT-authenticated access to a fleet of connected printers, print jobs, and the underlying parts library. Agents can register a JWT, list printers and their statuses, queue and inspect print jobs, and look up parts by ID. The API is the programmatic surface for Carbon's manufacturing platform used by production additive-manufacturing teams.
Install Jentic One Beta
Connect the Carbon REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Carbon REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbon.inc%2Fcarbon" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbon.inc%2Fcarbon" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Carbon REST API.
Register a JWT bearer token for subsequent API calls
List all Carbon printers connected to the account with their status
Retrieve detailed status and configuration for a specific printer by ID
Submit a new print job referencing a part for an available printer
List print jobs across the fleet with filtering and pagination
Inspect a single print job's progress and outcome by print ID
Look up parts in the part library by part ID for use in print jobs
Use Cases
Patterns agents use Carbon REST API for, with concrete tasks.
★ Automated Print Queue Orchestration
Drive a manufacturing workflow that selects an available Carbon printer, submits a print job referencing a part from the library, and polls for completion. The Carbon REST API exposes printers, prints, and parts as first-class resources, so an orchestrator can list idle printers via GET /printers, post a job to POST /prints, and watch progress on GET /prints/{printId} until status changes.
List printers, pick the first idle one, create a print job for partId PART-123 on it, then poll GET /prints/{printId} until status is complete.
Production Floor Monitoring Dashboard
Power an internal dashboard that shows live printer fleet status and active jobs. The API returns the printer list and individual printer detail, letting operators see which units are running, idle, or in error, alongside the print queue and per-job status. This gives production managers a single agent-readable view of additive manufacturing capacity.
Fetch all printers and all in-flight prints, then return a JSON summary of how many printers are busy, idle, or errored.
Parts Library Lookup for CAM Pipelines
Integrate Carbon's parts library into a CAM or PLM pipeline. The /parts and /parts/{partId} endpoints expose the part metadata Carbon needs for production, so an upstream system can validate that a given part exists and is ready before a job is submitted. This prevents queuing jobs against missing or stale parts.
Given a CAD identifier, call GET /parts to confirm a matching part exists in Carbon's library, then return the partId.
AI Agent Manufacturing Control via Jentic
Wire Carbon into an AI agent through Jentic so a natural-language instruction such as 'print 5 brackets on the first available printer' becomes a reliable tool call. The agent searches Jentic for the print-creation operation, loads the input schema, and executes with a JWT injected from Jentic's vault, with no Carbon credentials in the agent context.
Through Jentic, submit a print job for partId PART-456 to printerId PR-01 and confirm the job was accepted.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for carbon rest api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/register
Register a JWT bearer token
GET
/printers
List all Carbon printers
GET
/printers/{printerId}
Get a specific printer's status
POST
/prints
Create a new print job
GET
/prints
List print jobs
GET
/prints/{printId}
Get a specific print job
GET
/parts
List parts in the library
GET
/parts/{partId}
Get a part by ID
POST
/register
Register a JWT bearer token
GET
/printers
List all Carbon printers
GET
/printers/{printerId}
Get a specific printer's status
POST
/prints
Create a new print job
GET
/prints
List print jobs
GET
/prints/{printId}
Get a specific print job
GET
/parts
List parts in the library
GET
/parts/{partId}
Get a part by ID
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Carbon REST API
- AI-Aware (B+)70/100
93
Foundational Compliance63
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability75
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
40%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Carbon REST API by hand means minting a JWT bearer token via the register call, sending it in the Authorization header on every request, and calling the gw.carbon.inc host yourself. Through Jentic you install once, import the Carbon REST API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Carbon puts the printer id in the URL path (/printers/{printerId}), so a rule can pin your agent to one printer for status reads. You choose the operations it may call, so print job creation is not included unless you add it.
Credential isolation
Your Carbon JWT is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a 3D print job' or 'list printers', and Jentic returns the matching Carbon operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Carbon REST API through Jentic.
Why is there no official OpenAPI spec for Carbon REST API?
Carbon does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Carbon REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
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.
GET STARTED