Build Plate Co logo buildplateCo Custom 3D printed parts
Log in Get a quote

3D printing, through your AI agent

Ask your agent.
We’ll print your part.

Give your AI agent your 3D model and our website. It can get a quote, choose shipping, and take your order to secure checkout.

Open to everyone. Guest checkout, with no BuildplateCo account or API key to set up.

Get the prompt Upload a file yourself

Send this with your model

Start with a simple request.

Get this model quoted at https://buildplateco.com/order-with-ai/. Use guest checkout, show me the total with shipping, and use my authorized payment method or give me the secure payment link.

From file to checkout

The same order. Fewer steps for you.

  1. Give your agent the details

    Attach your STL or STEP file. Include quantity, material and color preferences, your U.S. delivery address, email, and budget.

  2. Review the complete price

    Your agent can get print pricing and a shipping total. Ask it to check the part settings, quantity, and delivery details before ordering.

  3. Complete secure checkout

    Your agent can open checkout with your approved order details. Use its supported payment tools, or open the secure payment link yourself.

A little context helps

Tell your agent what the part needs to do.

Indoor or outdoor use? Heat, load, or a particular finish? Add those details if you’d like your agent to help choose a material. A print-ready model is required for an instant quote.

Agents with browser access can use our regular quote and guest checkout pages. Agents with tool support can connect directly below. Payment capabilities vary by agent; your order is confirmed after payment succeeds.

Need help preparing a printable model?
Connect an agentMCP, API documentation, and ordering instructions

No customer login or pre-issued API key is required. Create a guest session, keep its temporary bearer token private, and use it for the customer’s quote and checkout.

MCP
https://buildplateco.com/mcpStateless Streamable HTTP tools
Text guide
/llms.txt

Guest API flow

  1. Read current printing options

    GET /api/agent/v1/catalog/ returns available material, color, and quality codes, default settings, file limits, and payment availability. Use these codes when requesting a quote.

  2. Create a session

    POST /api/agent/v1/sessions/ returns session_id, token, and expires_at. Send Authorization: Bearer <token> on subsequent requests. Cookies are not required.

  3. Upload and quote

    Send a multipart request to POST /api/agent/v1/sessions/{session_id}/quotes/ with the model in file and settings in material, quality, color, infill_percent, and orientation_mode. Include a unique Idempotency-Key so a retry can reuse the request.

    Read a quote at GET /api/agent/v1/sessions/{session_id}/quotes/{quote_id}/?quantity=1. Adjust the quantity as needed.

  4. Preview the full order

    Send POST /api/agent/v1/sessions/{session_id}/preview/ with the quote items and customer details. Use the returned shipping options and total to confirm the order with the customer.

    {
  "items": [{"quote_id": "<quote_id>", "quantity": 1}],
  "customer": {
    "full_name": "Customer name",
    "email": "customer@example.com",
    "shipping_name": "Recipient name",
    "address_line1": "Street address",
    "address_line2": "",
    "city": "City",
    "state_region": "OH",
    "postal_code": "44870",
    "country_code": "US"
  }
}

    Include shipping_option when selecting a shipping option.

  5. Create secure checkout

    After customer authorization, send POST /api/agent/v1/sessions/{session_id}/checkout/ with the preview and the agreed total.

    {
  "preview_id": "<preview_id>",
  "expected_total": "<agreed total>",
  "currency": "USD",
  "confirm": true
}

    The response includes checkout_url for secure payment and order_url for the order. Use the documented status endpoint to verify payment; creating checkout alone does not mean the order is paid. Keep private session and order links out of public logs.

Consult the OpenAPI specification for available settings, request headers, status endpoints, and error responses.