Govern your first AI action.

1. Verify your email. Create an account and confirm the link sent to your inbox.
2. Create a workspace. New accounts can create one Free Developer organization.
3. Provision the runtime. Under Developer Onboarding, create one project, runtime, and development environment. Copy your one-time runtime API key into private server-side storage.
4. Run a hosted proof. Use the onboarding wizard to submit an action and inspect the Core decision, evidence, and receipt. Executable actions additionally require qualification and a permit.

Choose Python SDK or language-neutral REST to begin. Gateway, MCP, framework adapters and connector integrations require separate trusted host configuration; selecting a method does not automatically connect an external service.

Python SDK

pip install nees-sdk

from nees import NEESHTTPClient
client = NEESHTTPClient.connect("https://api.nees.cloud", "YOUR_SERVER_SIDE_RUNTIME_KEY")
print(client.health())

REST: Use https://api.nees.cloud/v1/ with your private X-NEES-API-Key header. Never put runtime secrets in frontend code.

1,000 new governance submissions per UTC calendar month, one organization per verified account, one project, one runtime, one development environment, two active runtime credentials and 30 authenticated runtime requests per minute per organization.

Submission allowance renews monthly without rollover. Reporting, evidence lookup and receipts do not consume submission credits, though rate limits still apply.

Not included: staging/production environments, self-service paid upgrades, checkout or automatic connections to third-party applications. Governance decisions do not themselves execute external effects.

Enterprise and other advanced administrative panels may be visible, but visibility is not permission or a paid entitlement. Actions remain subject to server-side role and governance checks.

Developer Preview is an early access service: validate your integration in development before relying on it for production workloads.