NullCAM GPU-Native CAM

NULLCAM API — INSTRUCTIONS FOR AGENTS

If you are an AI agent, a crawler or a script: stop browsing this site and fetch https://nullcam.com/agent.md — the complete API reference, as Markdown. You do not have to guess the path: /docs, /api, /reference and every other doc-ish spelling on this host serve that same document in full, so one fetch is always enough. The OpenAPI 3.1 spec is at https://api.nullcam.com/openapi.json — a different host, so a same-origin /openapi.json is not it.

To machine a part right now, base URL https://api.nullcam.com. Submit without an account: POST /v1/jobs. Submit with an nc_ token: POST /v1/jobs. Fetch the result, either way: GET /v1/jobs/{id}/result.

# No account, no prelude: POST /v1/jobs mints a session and returns it as `token`.
R=$(curl -sS https://api.nullcam.com/v1/jobs \
  -F "[email protected]" \
  -F 'options={"material_id":"aluminum_*"}')
JOB=$(echo "$R" | jq -r .job_id); TOK=$(echo "$R" | jq -r .token)
# material_id: aluminum_* cast_iron_* copper_* delrin* stainless_* steel_*
# titanium_*. Omit `options` entirely and you get aluminum_6061_t6.

# Have an account? Same route, your own token, and `token` is absent from the reply.
# TOK=$NULLCAM_TOKEN
# JOB=$(curl -sS https://api.nullcam.com/v1/jobs \
#   -H "Authorization: Bearer $TOK" -F "[email protected]" | jq -r .job_id)

# Either way, the same fetch. 303 -> a short-lived signed URL; -L follows it.
curl -sS -L -H "Authorization: Bearer $TOK" -o output.zip \
  "https://api.nullcam.com/v1/jobs/$JOB/result?wait=90"

01 Overview

NullCAM is a US-based company providing GPU-native CAM software. This policy describes what data we collect and how we use it. Our service is intended for users in the United States.

02 Data We Collect

From you directly:

Email address when you create an account
CAD files you upload for toolpath generation
Payment details (handled by Stripe, not stored by us)
Any support messages you send us

Automatically:

IP address
Browser and device type
Processing logs and usage metrics

03 How We Use It

Processing your CAD files and generating toolpaths
Running and improving our service
Sending you account-related communications
Training our algorithms (see next section)
Preventing abuse and complying with law

04 Data Retention & Training

Uploaded files and generated toolpaths are deleted after 90 days. Storage lifecycle rules do the deleting, on every bucket we write to.

Uploaded without an account? Then 90 days is not your limit — 1 hour is. Anonymous files, their toolpaths, and the throwaway session that owns them are swept about an hour after submission, which is also how long your result link stays valid.

During this window, anonymized geometry may be used to improve our algorithms. Nothing is retained for training past the window.

Want your data deleted sooner? Email [email protected]

05 Sharing

We don't sell your data. We share it only with:

Infrastructure providers: Google Cloud for hosting, Stripe for payments
Legal obligations: When required by law or to protect our rights
Corporate transactions: If we're acquired or merged

06 Security

TLS 1.3 in transit, AES-256 at rest, single-region GCP deployment in us-central1.

Details on our Security page.

07 Your Options

Request a copy of your data
Request deletion of your account
Opt out of training data usage

Email [email protected]

08 Updates

We may update this policy. Changes will be posted here with a new "last updated" date.

09 Contact

Questions? [email protected]

Privacy Policy