Skip to main content
Noetfield API

Developer preview

Noetfield API

OpenAI-shaped engine endpoint · schema-valid JSON and tool calls · commissioning lane

Commissioning preview for developers evaluating a governed API surface. Compatibility is tested per provider family — not claimed as universal production readiness.

Request workspace access View applications

Commissioning preview scope

Structured completions under deterministic controls.

Developer preview lane for evaluating schema-valid JSON and tool-call behavior — not a production corporate product surface.

Schema-valid or fail

JSON and tool calls must validate before the response leaves the API — repair or fail closed on failure.

Coding Pro lane (commissioning)

Evaluated in workspace when enabled. Model noetfield-coding-pro — planner + stronger coding matrix under commissioning controls.

Provider families (commissioning)

Additional wire formats may be enabled per tenant during commissioning evaluation — each tested within stated scope, not as a universal three-protocol guarantee.

Fail-closed is easy to assert and hard to show, because the case worth seeing is the one where the model is wrong and something stops it. The Research Trader runs that case in public every morning against market data, and publishes each refusal with the arithmetic reason attached. It demonstrates that the check runs and rejects; it does not demonstrate that this API is correct for your schema.

Access

Create your API workspace

Commissioning preview: register a workspace email to evaluate the API lane. Keys are generated only after sign-in — never on this public page.

  • Email creates your tracked tenant for commissioning evaluation
  • Generate API keys inside the signed-in workspace
  • Billing and balance features appear only when the commissioning lane is enabled for your tenant

Opens your signed-in workspace. Generate the API key there.

Commissioning note

Billing is workspace-scoped during evaluation

This public page does not advertise production pricing, trial promotions, or paid top-ups. Signed-in workspace tenants see billing controls only when the lane is enabled for commissioning.

  • Register or sign in for workspace access
  • Keys and lane status appear inside the signed-in workspace

Already registered? Open the workspace to manage billing.

Sign in to workspace New here? Request access

Infrastructure

Engine endpoint for structured completions

Use Noetfield API when you need OpenAI-compatible completions under schema validation. For governed workflows with authority and receipts, start with AI Motors.

Explore AI Motors

Reference: request, response, receipt

The shapes below are documentation samples. They show the contract shape; they are not recorded runtime output. Endpoint activation is per workspace tenant during commissioning, so the public path answers only for enabled tenants.

Sample request · shape only

POST /v1/chat/completions
Authorization: Bearer sk-nf-<workspace key>
Content-Type: application/json

{
  "model": "noetfield-deterministic",
  "messages": [{ "role": "user", "content": "<task>" }],
  "response_format": {
    "type": "json_schema",
    "json_schema": { "name": "<name>", "schema": { "…": "…" } }
  }
}

Sample response · shape only

{
  "choices": [{
    "message": { "role": "assistant", "content": "<schema-valid JSON>" },
    "finish_reason": "stop"
  }],
  "nf": {
    "schema_valid": true,
    "repair_attempts": 0,
    "receipt_id": "rcpt_<id>"
  }
}

Receipt schema · shape only

{
  "receipt_id": "rcpt_<id>",
  "lane": "deterministic-api",
  "schema": { "name": "<name>", "validated": true },
  "verification": {
    "attempts": [{ "n": 1, "result": "pass" }],
    "repair_attempts": 0,
    "repair_bound_reached": false
  },
  "boundary": "a receipt is not certification"
}

Errors and safe stop

The lane fails closed. If output cannot validate against the declared schema within the bounded repair budget, the request returns an error identifying the failed criterion instead of partial or unvalidated output. Provider routing stays behind the endpoint: your integration binds to the schema contract, not to any single upstream model, and provider families are enabled per tenant within tested scope.

Current limitations

Developer preview under commissioning. Endpoint activation, billing, and keys are workspace-scoped. Compatibility is tested per provider family within stated scope; universal SDK compatibility and production readiness are not claimed. No uptime commitments are published for the preview lane.

The developer surface

API

Schema-valid-or-fail structured completions under deterministic controls, with workspace keys.

Reference on this page

AI Motors

The governed execution runtimes underneath every surface: authority, bounded workers, separate verification.

AI Motors

Contracts and schemas

Request, response, and acceptance-contract shapes, all labeled sample or shape-only until shipped.

Shapes · Evidence bundle example

Receipts

What an accepted outcome preserves, and the boundary that a receipt is not certification.

Evidence register