REST API

The MCP tools are also plain HTTP endpoints. Same names, same arguments, same bearer key.

Authentication

Every request carries Authorization: Bearer sc_…. The key is minted in the studio under Settings → Design from your own AI agent.

List the tools

GET https://app.koppar.ai/api/agent/tools

Returns { "tools": [ … ] }. Each entry has name, title, description, read_only, destructive and input_schema (JSON Schema).

Call a tool

POST https://app.koppar.ai/api/agent/tools/<name>
Content-Type: application/json

The body is the tool’s arguments. The response is the tool’s result as JSON.

curl -s https://app.koppar.ai/api/agent/tools/create_design \
  -H "Authorization: Bearer sc_…" \
  -H "Content-Type: application/json" \
  -d '{"brief":"USB-C powered ESP32-C3 board with a BME280 over I2C","title":"ESP32-C3 sensor"}'

Status	Meaning
200	The tool ran. The body is its result.
400	Arguments did not match the schema. `issues` lists the paths.
404	Unknown tool name.
4xx with `detail`	The tool refused: no such design, no circuit yet, a board already running.

Downloads

get_downloads returns one URL per artifact under https://app.koppar.ai/api/result/<design id>/…, each with available and, when not available, a note saying why. Fetch them with the same bearer header.

Artifact	Available when
`circuit.py`, `netlist`, `schematic.zip`, `bom.csv`, `project.zip`	A circuit has compiled
`board.kicad_pcb`, `board.glb`	A board exists
`gerbers.zip`, `order.zip`	The board has zero serious DRC errors and nothing unconnected

See the MCP page for the tool list and what each one does.

Start

Your own agent

Free tools

Engine

Reference

Authentication

List the tools

Call a tool

Downloads

​Authentication

​List the tools

​Call a tool

​Downloads

Authentication

List the tools

Call a tool

Downloads