Use Customize → Credentials for supported service accounts. Use Models for chat-model access, Local models for compatible local endpoints, and Compute for its dedicated remote-resource connections.
Connect a service
- Select the service in Credentials.
- Enter the fields shown for that account.
- Save the connection.
- Test it through a small supported operation.
- Confirm the intended account and its access before larger work.
Do not paste secrets into conversation text or project files. A saved credential supplies account access; it does not install software or add every feature of that service.
Research and integration connections
| Service entry | Fields | Intended use |
|---|---|---|
| GitHub | Access token | Authorized repository and API workflows. |
| Literature access | API key | Supported literature retrieval with your own access. |
| Firecrawl | API key | Your own web and research-search access. |
| OpenAlex | Contact email, optional API key | Scholarly records with your configured access. |
| NVIDIA API | API key | The ten NVIDIA BioNeMo NIM adapters (Boltz-2, DiffDock, Evo 2, GenMol, MolMIM, MSA Search, OpenFold2, OpenFold3, ProteinMPNN, RFdiffusion) billed to your NVIDIA account; workflows follow the BioNeMo Agent Toolkit. |
| NVIDIA NGC Registry | NGC API key | Approved BioNeMo container access for supported workflows. |
| Hugging Face | Access token | Authorized models, datasets, and Hub material. |
| Tinker | API key, optional base URL | Compatible training and inference workflows. |
| Weights & Biases | API key | Experiment-management workflows you explicitly configure. |
| Pinecone | API key | Compatible vector-index and retrieval workflows. |
| LangSmith | API key | Compatible evaluation workflows you explicitly configure. |
These entries describe user-configured integrations. Their presence does not mean OpenScience automatically sends every project or experiment to them.
Cloud-account fields
| Service entry | Fields shown |
|---|---|
| AWS | Access key ID, secret access key, optional default region. |
| Google Cloud | Service-account JSON and optional project ID. |
| Microsoft Azure | Account fields such as tenant, client, subscription, key, or endpoint, as required for the intended workflow. |
Cloud credentials do not add a general compute-job adapter. Use Remote compute for the supported job targets and provider-status connections.
Shared and personal access
Your selected account workspace may provide a shared connection. A saved personal key or explicit provider environment setting can take precedence. Confirm the account used by the operation when working across personal and team projects.
Use Ace and your account for funding-workspace selection and shared-connection sync. Changing a credential does not cancel a service subscription or a running external job.
Replace or remove access
Update the saved credential when rotating a key, then test a small request. Remove the connection when it is no longer needed, and revoke the old key at the service when appropriate.
For an authentication error, check the service entry, required fields, account permissions, and whether the service is enabled in its own setup panel. Share the error and operation name when seeking help, without the credential value.