Developer Preview / Core V3
Your first governed action.
From setup to evidence.
Create a Free Developer account and try the hosted governance proof. Then connect your trusted backend and verify decisions, execution outcomes and evidence.
1–2 / Prepare & publishAuthorized workspace setup and governance changes.
3 / Resolve & exportRead-only lookup; no credential or permission grant.
4–6 / Integrate & verifyBackend lifecycle, truthful reports and evidence.
01 / Prepare
Create your workspace and credential
- Create a free account and verify your email at app.nees.cloud.
- Create your Free organization, then use Developer Onboarding to provision one project, one runtime and a development environment.
- Issue the appropriate runtime credential through your authorized workflow and securely store it. Keep it in your trusted backend or secret manager.
Free Preview includes 1,000 new governance submissions per UTC month, one development environment, two active runtime keys and 30 requests/minute per organization. Staging, production and paid upgrades are not available on Free. Run the hosted onboarding proof before integrating a real external action.
Never put a runtime key in browser JavaScript, screenshots, prompts or public examples. A configuration export is separate from your credential.
02 / Define the boundary
Register the genuine supported action
Set its real resource, operation, capability and side-effect attributes. Publish the necessary authority, policy and relationship/tool governance state through an authorized workflow. Copying example identifiers does not provision an action.
Action prerequisites and public integration contract ↗03 / Read the existing baseline
Resolve existing assessment
- Open Infrastructure → Assessment configuration manager.
- Select the correct Project, Runtime and Environment.
- Choose Registered action → Published scope → Integration method.
- Select Resolve existing assessment for a permission-checked, read-only lookup.
- Inspect and export the supported version-bound configuration.
The export carries current assessment commitments, including refs, versions and digests. It contains no API key and grants no permission. Never invent the values manually. It can become stale when governance changes.
“Publish baseline & resolve” changes governance. This creates active authority only for a missing action baseline through an atomic, create-only Core operation. It refuses existing or customized commitments rather than overwriting them. Never use publication just to fix an assessment mismatch: inspect the current governance state and use a reviewed change workflow.
No action, no scope, or an export error?
Verify the selected runtime, registration and current published scope. A 409 means the expected baseline is missing or mismatched; inspect it rather than guessing or republishing. For 401/403 check account permissions; for 404 check resource selection; for 503 retry when the read service is available.
04 / Connect a trusted backend
Use the supported connector contract
Choose the method below. For Python, PyPI lists nees-sdk 3.0.0rc2, requiring Python 3.11+ (rechecked 17 October 2026). Confirm compatibility with your Runtime before use.
python -m pip install "nees-sdk==3.0.0rc2"Python client setup and environment conventions
import os
from nees import NEESHTTPClient, NEESHTTPConfig
client = NEESHTTPClient(NEESHTTPConfig(
base_url="https://api.nees.cloud",
api_key=os.environ["NEES_RUNTIME_API_KEY"],
timeout_seconds=20.0,
))
# Client setup only. No operation is sent.Constructor signatures are documented in the Developer Preview SDK reference. This is setup, not an authenticated end-to-end example. NEES_RUNTIME_API_KEY here is your application’s environment variable; the published SDK/CLI environment names are NEES_BASE_URL and NEES_API_KEY, with an optional HTTP timeout. Match the configuration contract of your selected interface.
05 / Govern, enforce, report
Submit → qualify → start → report
- Submit: send the registered action and current assessment through the matching public contract.
- Qualify: obtain valid governance qualification. Missing, stale or negative governance is not authorization.
- Start: follow the supported start contract only when authorized. Your app checks the actual target and context before performing the external effect.
- Report: verify and truthfully report the real result, including failures.
- Evidence → receipt: inspect available records and reconcile authorization, execution and verification.
ALLOW ≠ executed. A timeout proves neither permission nor execution. Fail closed and reconcile uncertain requests before retrying side effects.
06 / Evaluate before production
Test more than the happy path
Exercise an allowed operation, a denied operation, stale configuration, transport failure, target mismatch and external execution failure. Verify that reports, evidence and receipts match the actual effects. Check duplicate/retry behavior and credential rotation in your deployment.
Developer Preview supports evaluation and integration testing. Production readiness requires deployment-specific acceptance evidence.
| Case | Required observation |
|---|---|
| Allowed | The application still validates the live target; ALLOW alone is not success. |
| Denied or stale | No external effect occurs and no guessed assessment is substituted. |
| Runtime unavailable | The action fails closed; availability is never interpreted as permission. |
| Execution failure or uncertainty | Report the observed outcome and reconcile before any side-effecting retry. |
Python SDK / Developer Preview
A direct path for Python agents.
Overview
Connect a trusted Python backend to the hosted Runtime with the public NEESHTTPClient.
Requirements
Python 3.11+, a compatible Runtime, a registered action, a server-side runtime key and current assessment bindings.
Responsibility boundaries
Your service enforces decisions, validates the actual target, executes and reports the real outcome.
Documentation
Open Python SDK documentation ↗Setup
- Resolve the existing assessment in Dashboard.
- Install the compatible SDK in your backend.
- Use submit → qualify → start → report; inspect evidence and receipt.
Example
Published release candidate · rechecked 17 Oct 2026
python -m pip install "nees-sdk==3.0.0rc2"Limitations
Installing the SDK does not register an action or grant authority. Validate API compatibility for your deployment.