Integration methods / check exact deployment support

How to integrate NEES

Choose one supported route for your actual action path. Implementation somewhere in the NEES ecosystem does not mean every connector or framework is public, enabled or compatible with every account and deployment.

Open docs hub →Preview access and limits →

Python SDK — documented Developer Preview

Published V3 governance client: nees-sdk 3.x release-candidate family (3.0.0rc2 documented as checked 9 October 2026); requires Python 3.11+. NEESHTTPClient integrates a compatible trusted backend with the hosted Runtime.

It does not register the action, grant permission, or perform your external effect. Resolve the current assessment and test the lifecycle in your environment.

Python SDK product page →SDK usage and CLI ↗PyPI project ↗

REST API — version-matched backend contract

Trusted non-Python or Python backends can use a deployed, compatible HTTP contract. The public base is https://api.nees.cloud and a documented operation submission route is POST /v1/operations. This is not a complete OpenAPI promise: authentication details, remaining routes and schemas must be checked against the deployed version.

Integration contract and safety ↗

Gateway / Proxy — mediated supported routes

Use a configured supported proxy route for backend tool/service calls. Only calls actually mediated by that deployment are governed. Specific route mappings, availability and credentials need deployment-level verification.

Connector patterns ↗

MCP — supported host and tool boundary

An MCP adapter can connect a compatible host/tool route to the governance lifecycle. A Dashboard assessment export is not a complete MCP server configuration. Verify the named adapter, host, action mapping and version before claiming support.

Assessment and MCP configuration notes ↗

Framework adapters — named hook coverage only

Framework integrations can connect supported action hooks. They do not confer automatic universal coverage across every framework, plugin, or version. The owner must verify the actual tool path, failure semantics and outcome reporting.

Framework integration patterns ↗

Required boundary checks

  • Keep NEES/runtime/provider credentials on trusted backends, never in a browser.
  • Register the actual resource, operation, capability and side effect.
  • Obtain version-bound governance commitments through authorized setup; do not invent them.
  • Fail closed for negative/unavailable governance, verify live targets and report real outcomes.
  • Ask for specific connector availability before designing production dependency on it.