Skip to developer content
Hosted Evaluate · controlled free soak2026-09-16.beta2 · restricted access · x402 off · not GA. Selection is not execution. Offline kit: 2026-09-16.beta1 pinned teaching snapshot.
DeltaX EvaluateDEVELOPER PREVIEWGet started
Live 2026-09-16.beta2 · pinned kit 2026-09-16.beta1

Connect your agent.
Keep control of the handoff.

Wrap candidate generation with a small adapter, validate the evaluation response, and handle selected and refused outcomes explicitly. Start with the pinned offline kit; hosted access remains restricted during controlled soak.

Start onboardingDownload the kit
A · Operational stateControlled free soak
Request routePOST /v1/evaluations
Live API version2026-09-16.beta2
AccessRestricted · not GA
B · Offline kit2026-09-16.beta1 pinned
Selection / x402Never executes · x402 disabled
Integration responsibilities

One API boundary.
Four jobs for your client.

Place the adapter between candidate generation and application handling. The details below describe the pinned beta1 offline contract; an approved hosted integration must use its assigned runtime version and configuration.

  1. 01 · Build the request

    Map into the fixed profile.

    Send profile_id, objective, bounded context, and 1–8 candidates. Each candidate includes a unique ID, semantic class, description, and operator-reported support.

    Review classes: analyze, compare, draft, validate. The external class is shadow-only.

  2. 02 · Submit deliberately

    Bind identity and retries.

    The contract defines POST /v1/evaluations with a bearer credential, an API version, and an Idempotency-Key. Credentials and tenant access come from approved hosted onboarding.

    Reuse a scoped key only for the same request. A changed request digest with that key returns 409; changed input needs a new evaluation.

  3. 03 · Validate the response

    Handle both governed outcomes.

    Validate the response schema and version. Read outcome, selected_candidate_id, reason_codes, trace, and authority.

    selected identifies a submitted eligible candidate. governed_noop_refusal returns a null selection. Errors and invalid responses must stop this path; apply the documented retry rules.

  4. 04 · Own the next step

    Separate evaluation from effects.

    Persist the decision receipt and connect it to your workflow record. Your application retains execution permission, tool credentials, outcome recording, and the decision to re-evaluate.

    The response reports external_effect=false and learning_applied=false. Temporal memory across the wider system is an explicit integration responsibility.

Prepare locally: the kit contains schemas, synthetic request/response specimens, and selected/refusal fixtures. It does not provision credentials or a public live endpoint.

Read the exact beta1 contract
Five-minute offline path

Download and verify. Render both outcomes. Fail closed.

Download the pinned offline kit, then run the remaining steps from its extracted root. Every command uses synthetic contract specimens and makes no network request. This page does not offer public signup or unrestricted credentials; hosted soak access stays allowlisted and separately governed.

  1. 01 · Download

    Get the pinned kit and checksum

    Use the versioned ZIP and its SHA-256 sidecar. The bundle holds the frozen contract, fixture matrix, and standard-library reference client.

    Download ZIP ↓Open SHA-256 ↗
  2. 02 · Verify

    Run the offline verifier

    python3 conformance/run.py

    Run from the extracted kit root. It uses only the Python standard library and checks integrity, fixtures, closed authority flags, and fail-closed client behavior.

  3. 03 · Selected

    Render the selected request

    python3 python/deltax_client.py --fixture fixtures/cases.json --case selected

    Inspect the serialized request, then compare it with the paired selected response. The returned candidate is still not executed or authorized.

  4. 04 · Refusal

    Render the refusal request

    python3 python/deltax_client.py --fixture fixtures/cases.json --case refusal

    Compare the external-only request with its paired governed_noop_refusal response. No candidate passes into action.

  5. 05 · Fail closed

    Inspect malformed and unknown cases

    • unknown_top_level_field
    • wrong_profile
    • unknown_semantic_class
    • duplicate_candidate_id
    • nested_context

    Unknown shape, profile drift, duplicate identity, or nested context stops locally. Do not invent a retry, fallback, or downstream action.

    Open the complete fixture matrix ↗
Five steps · synthetic specimens · zero endpoint callsInspect both governed outcomes →

No public signup. Hosted soak access uses OAuth 2.0 client_credentials with the deltax:evaluate scope for allowlisted, server-owned principals only. This page does not issue credentials. Do not invent a credential, retry, or downstream action.

Complete offline bundle · ZIP

DeltaX Evaluate Developer Kit

Human guidance, the pinned beta1 OpenAPI design snapshot, the fixed profile manifest, examples, fixtures, and a fail-closed Python client. Live soak uses beta2; this kit remains the historical offline contract resource.

Download offline kit 2026-09-16.beta1 ↓For people · Markdown

Onboarding Guide

Work through the contract boundary, offline fixtures, client checks, and the exact stop conditions before integration.

Open guide ↗Machine contract · OpenAPI 3.1

Hosted Evaluation Contract

Inspect the closed request, response, trace, authority, and error schemas for the pinned beta1 teaching snapshot.

Open OpenAPI ↗Fixed profile · JSON

Profile Manifest

Pin the only admitted profile, the teaching-fixture label, and every non-authority boundary without exposing a registry.

Open manifest ↗
Also in the kitGenerated reference ↗Python client ↗cURL walkthrough ↗Agent contract ↗ZIP checksum ↗
Paired contract views

People and agents see the same boundary.

Choose a topic to pair a plain-language explanation with a structured integration summary.

Human GuideOverview
Plain language

One bounded hosted-evaluation design

What it means

The contract accepts one bounded objective, scalar context, and a finite candidate field. It returns either one selected submitted candidate or a governed no-op refusal with a reviewable trace.

Example

A client can model a synthetic review with analysis, comparison, drafting, validation, and external candidate descriptions, then practice handling the resulting trace without performing any candidate.

Boundary

The hosted runtime is in controlled soak with restricted access. The offline kit remains a pinned beta1 snapshot. Neither grants public unrestricted access, GA, or execution authority.

Agent Contract · designOverview
{
  "title": "DeltaX Hosted Bounded Review Evaluation API",
  "offline_kit_api_version": "2026-09-16.beta1",
  "live_soak_api_version": "2026-09-16.beta2",
  "method": "POST",
  "path": "/v1/evaluations",
  "profile_id": "deltax-hosted-bounded-review-evaluation-v1",
  "result_mode": "bounded_non_consequential_review",
  "operational_state": "controlled_free_soak",
  "generally_available": false,
  "submitted_candidate_executed": false,
  "grants_downstream_authority": false,
  "x402_admission_enabled": false
}

These views summarize the pinned offline design contract for onboarding. The versioned OpenAPI in the kit is the beta1 snapshot; the hosted runtime under controlled soak speaks beta2. Neither artifact grants public access or execution authority.

Only developer-facing protocol fields and synthetic examples are included in these views.

Teaching fixture

Synthetic Evidence Review

A harmless scenario for learning how a finite candidate field is represented and how the external class remains shadow-only.

Fixture label · not a wire-level domain

Synthetic Evidence Review

Choose the next bounded review step for a synthetic evidence packet. The design evaluates submitted descriptions without fetching, altering, publishing, or acting on the packet.

Wire profile
deltax-hosted-bounded-review-evaluation-v1
Scenario status
Offline teaching fixture
External effects
False
analyzeSummarize the evidence gapsSelectable only if every gate passes
compareCompare two synthetic support claimsSelectable only if every gate passes
validateValidate the packet shapeSelectable only if every gate passes
externalPublish the packetRecorded as shadow-only · never selectable
Outcome 01

selected

One submitted non-external candidate passed every gate. It is returned for review and is still not executed or authorized.

Outcome 02

governed_noop_refusal

No submitted candidate passed the complete gate set. The receiving client stops and presents the bounded reason codes.

Delivery maturity

Operational soak, offline kit, and unresolved stay separate.

The hosted controlled-soak runtime, the pinned offline developer kit, and future public-access work are three different claims with three different authority boundaries.

  1. Current

    Hosted controlled free soak

    2026-09-16.beta2

    A controlled free soak of the hosted evaluation runtime with restricted, allowlisted access.

    Call
    POST /v1/evaluations
    Caller check
    OAuth 2.0 client_credentials · deltax:evaluate
    Decision evidence
    Reviewable trace · selection never implies execution
  2. Pinned offline kit

    Frozen developer contract snapshot

    2026-09-16.beta1

    Wire snapshot
    Offline OpenAPI · fixtures · fail-closed client
    Profile and auth
    One fixed profile · OAuth client-credentials design shape
    Availability
    Historical/pinned kit · not the live soak version
  3. Unresolved future

    Public access, GA, and commercial activation

    A successor must separately authorize anything beyond restricted soak access.

    • Public credential issuance and unrestricted customer access
    • General availability, SLA, and broader identity lifecycle
    • Paid/customer x402 admission (disabled during soak)

    Separate approval required

x402 disabled during soak

Payment would not change gates or authority.

Expansion boundary

One fixed profile. Broader domain work stays separate.

The developer preview intentionally avoids a public domain registry and arbitrary profile selection. Broader domain work requires its own governing records, tests, review, and separate explicit authorization.

A teaching fixture is not a domain approval or an activated API profile.

Do not derive new semantics, public customer access, unrestricted credentials, or action authority from this preview.