This page describes what your AI agent can do with Chiplab.
You don’t need to call anything yourself, just ask your agent to build your firmware and it takes care of the rest.
This is a reference for the curious, not a set of instructions for you to follow.
Listing builds
list_jobs returns the project’s jobs, most recently started first.
string
required
The project whose builds you want.
string
Pass
build to list builds only. Omit it to list runs and builds together.string
An RFC 3339 timestamp. Only jobs started before this time are returned. When
more_available is true, pass the created_at of the last job in the page to continue.string
Identifier for this build. Pass it to
wait_for_job to read the result.string
Where the build is in its lifecycle.
string
When the build started.
job_id to wait_for_job for what the build produced.
Reading the result
wait_for_job blocks until the build finishes or the timeout elapses.
string
required
The
job_id from list_jobs, or the id returned when the build was started.number
How many seconds to wait. The server caps this value.
string
running, succeeded, or failed.object
What the build was started with, so a build from an earlier session can be recognized on its own.
object
Present when
status is succeeded. Includes an artifacts list naming the files the build produced.string
Present when
status is failed. What went wrong.status: "running" and timed_out: true means the build is still going.
Calling wait_for_job again on a finished build returns the same response immediately.
Downloading artifacts
issue_download_ticket takes the job_id and an artifact_name from the result’s artifacts list.
It returns a presigned download_url.
A GET of that URL returns the artifact bytes, with no auth header.
A succeeded build’s artifacts are what a later run can execute, once your agent has an artifact_id for that project.