The developer surface
Nexplora exposes several ways to work with the product. They do not share authority: installation, authentication, discovery, company state, and external effects remain separate and explicit.
API
Authenticated application and SDK surfaces are for the operator's own workspace. Use an API key created in MY → Developer and keep it server-side; the public discovery pages do not grant API access.
MY → Developer →Discovery MCP
A public, read-only JSON-RPC catalog for departments, use cases, and recommendations. It is not the authenticated operator MCP and cannot access private company records or run actions.
Open MCP →A2A Agent Card
A public discovery card at the standard well-known location. It describes the bounded discovery endpoint; it is not a permission grant or an external-effects executor.
Agent Card →Check CLI availability
The NX CLI is in private beta with no public installer. Contact Nexplora for access and setup instructions.
Authentication: private API and operator actions require an authenticated Nexplora workspace and an API key or session issued through the product.
MCP: the public endpoint is discovery-only. Authenticated operator MCP capabilities are a separate surface and are still subject to account permissions, connection state, approval policy, and effect verification.
A2A: the agent card improves discovery; it does not make private company context public and does not authorize an external agent to act.
Versioning: treat public URLs and the JSON-RPC protocol response as versioned contracts. Re-check the live endpoint and account documentation before building a production client.