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 →Public discovery
A public, read-only catalog for departments, use cases, and recommendations. It cannot access private company records or run actions.
Explore the catalog →Connected apps
Connect an AI app to your Nexplora workspace. Access stays behind sign-in, your permissions, and Nexplora's approval rules.
Connect an AI app →Start here
Call the Nexplora API
Use this base URL for the REST API. Create a key in MY → Developer, keep it on your server, and send it in the Authorization: Bearer header.
https://nexplora.ai/api/v1curl "https://nexplora.ai/api/v1/capabilities" \
-H "Authorization: Bearer $NEXPLORA_API_KEY"Never put an API key in browser code or commit it to source control. The capabilities endpoint returns capability packs for the authenticated workspace.
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.
Public discovery: the catalog helps an assistant learn what Nexplora offers, but it cannot see your workspace or authorize an action.
Connected apps: the connection at /mcp is the private path for an AI app to use your workspace after you sign in and choose its access.
Protocols: JSON-RPC is a versioned contract, and the A2A agent card is the discovery contract for compatible agents. Treat published URLs and response shapes as contracts.