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 Infrastructure

✓
Single-region GCP
All data resides in Google's us-central1, defined in Terraform.
✓
Encrypted
TLS 1.3 in transit, AES-256 at rest.
✓
Locked Down
Geometry workers run on read only filesystems with network access restricted to only internal routes.
✓
No third-party kernels
No Parasolid, ACIS, or licensed code, and tight control of the geometry stack.
✓
Minimal third-party provider use
The only external provider is Sendgrid for sending transactional emails.

02 Data Retention

✓
90-day auto-deletion
Automatic retention policies for files, toolpaths, and messages remove everything after 90 days. This is enforced by storage lifecycle rules on every bucket we write to, not by application code remembering to run.
✓
Anonymous uploads: 1 hour
If you upload without an account, 90 days does not apply to you. The file, the toolpath, and the throwaway session are swept about 1 hour after submission — the same window in which your result link works.
✓
Deletion on request
Email [email protected] for deletion of models added to our test corpus with "help improve NullCAM" reports.
✓
Training data
Geometry may be used to improve our algorithms during the 90-day retention window. Nothing is kept past it.

03 SOC2 Type II

SOC2 Type II certification is planned. If you need it, email [email protected] and we'll tell you when it ships.

Current Security Status

Beta

Product Stage

GCP

Infrastructure

90 days

Data Retention

Planned

SOC2 Type II

CAD files are sensitive.

01 Infrastructure

02 Data Retention

03 SOC2 Type II