Integrations
The connector catalog, how connectors disclose their read-only tools, and the tiers that show what is available now.
Integrations are how your operational data reaches the platform. A connector is a configured link to an external system that wraps its API as a set of typed operations, so the same actions look identical no matter which underlying system fulfills them. Connecting those systems is what Nucleus does, and the connector catalog is where you do it.
The connector catalog
You add a connector the way you add a service: pick it from the catalog and onboard it. Connectors are organized by category:
- Dispatch and scheduling. Your dispatch and trip systems.
- Billing and payments. Your billing and payment systems.
- Fleet and vehicle management. Telematics and vehicle systems.
- Identity providers. Single sign-on and directory sources.
- Regulatory and knowledge corpora. Reference sources the assistant can cite from: the regulatory corpus behind Compliance Link, an operator configuration knowledge base, and public community-resource directories. These hold public reference material and carry no rider or trip data.
Read-only tool disclosure
When a live connector is enabled, it can expose tools to AI Studio so the assistant can work with that system's data.
Every disclosed tool is read-only. The assistant can read through a connector but cannot take destructive actions: write tools are withheld from agent surfaces. The catalog shows exactly which read-only tools a connector exposes, so there are no hidden capabilities.
Availability tiers
Connectors are tiered so you can see what is ready now and what is coming:
- Live. Available to enable today, with its read-only tools disclosed.
- Coming soon. On the near-term roadmap.
- Future. Planned, listed so you can see the direction.
If a source you need is not in the catalog, you can request a custom integration.