Choose an interface
Use the browser, an AI assistant, REST, an SDK or the terminal for the same evidence workflow.
Choose the interface that fits how you work. CyberRXN provides a browser app, a remote MCP connection and an authenticated REST API. The Python and JavaScript SDKs and their CLIs call that API.
Pick a starting point
| Interface | Good starting use | Setup |
|---|---|---|
| Browser app | Explore records and inspect your workspace without writing code | Sign in and choose a workspace |
| ChatGPT or Claude through MCP | Ask a question and have an assistant retrieve and explain evidence | Connect MCP with OAuth |
| REST with cURL | Try a request or integrate from another language | First API request with a workspace API key |
| Python SDK | Notebooks, data processing and Python services | Python guide and verified package |
| JavaScript / TypeScript SDK | Node.js scripts and services with typed requests | JavaScript guide and verified package |
| CLI | Work from a shell or call the service from scripts | CLI guide after installing either SDK package |
You can use more than one interface. For example, explore a question in the app, reproduce it in a notebook and give an assistant access through MCP. Keep the intended CyberRXN workspace consistent when comparing access and usage.
Account, workspace and credentials
The browser uses an app session. MCP normally uses OAuth, with a CyberRXN workspace selected during consent. REST and SDK examples use a workspace API key from API keys.
These credentials are not interchangeable. An API key does not acquire first-party-session or review permissions. Changing the selected workspace in the dashboard does not move an existing MCP connection; reconnect and choose the intended workspace when approving access. Authentication and workspaces.
For SDKs, provide CYBERRXN_API_KEY through the environment or use the credential options documented by the client. Python and the CLIs can use a saved CLI login; the JavaScript SDK itself does not read that login. Keep API keys in a private runtime, not in browser code or an assistant conversation.
Install from the current distribution
Use the installation guide for the actual Python and JavaScript archives and SHA-256 checksums. The package is not currently published to the public npm or PyPI registry. Do not substitute a registry package with a matching name for the documented download.
Connecting MCP does not require installing either SDK. It also does not install a local filesystem skill: the agent reads the hosted guide and current action catalog from the server. MCP guide.
Verify your setup
- App: confirm the selected workspace before reading records or changing controls.
- MCP: inspect actual tool activity. The guide should be read before chemistry work; a source-backed answer needs a search and a full observation.
- REST or SDK: use the non-billable usage request to verify access, then run the bounded chemistry example in the quickstart.
- CLI: verify the configured credential and use the commands shown in the CLI guide.
Successful chemistry calls consume usage regardless of which interface initiates them. An assistant can perform more than one operation for a single question. Read usage and billing and apply rate controls before a batch.
Continue with a complete task
Follow from a molecule to source evidence for the search-and-read sequence. Use task recipes for exact transformations, atom balance and conversion. For exact request and response fields, open the API reference.