Carbon REST API

Name: Carbon REST API API
Brand: Carbon REST API
Availability: InStock

★ Only Publicly Available SpecIOTDevice Managementbearer8 EndpointsREST

For Agents

Queue and monitor 3D print jobs on a Carbon printer fleet, list connected printers, and look up parts in the manufacturing library.

Quickstart

Get started with Carbon REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a 3d print job"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Carbon REST API API.

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

GET STARTED

Start building with Carbon REST API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Carbon REST API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Carbon REST API 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

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Carbon JWTs are stored encrypted in Jentic's vault. Agents receive scoped execution rights only — the JWT is injected into the Authorization header at request time and never enters the agent's prompt or chat logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a 3d print job' or 'list printers') and Jentic returns the matching Carbon operation with its input schema, so the agent picks the right endpoint without docs lookups.

Time to first call

Direct Carbon integration: 1-2 days for JWT registration flow, error handling, and polling logic across the eight endpoints. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CarbonAPI

CO2 emissions calculations for products, journeys, and energy use.

Use alongside Carbon REST API when reporting the embodied carbon of additively manufactured parts.

Complementary

CarbonDoomsday

Atmospheric CO2 readings from Mauna Loa for sustainability dashboards.

Pair with Carbon when surfacing global CO2 context next to factory-level manufacturing data.

Alternative

Carbon Black

Unrelated cybersecurity API; included as a disambiguator only.

Do not select for 3D printing — Carbon Black is an endpoint security API, not a manufacturing one.

FAQs

Specific to using Carbon REST API 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 at https://app.jentic.com/sign-up.

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.