Introduction
UnifyApps connects to Core42 Compass and returns what that account serves, so it can be inventoried, monitored and brought under policy alongside every other platform you run.
Core42 Compass returns models only: a sweep finds the models available on your account, and you import them into the Model Registry. There are no agents to discover.
What UnifyApps discovers
Discovery reads the platform's own APIs through a connection your tenant already holds. The models it serves can be imported into the Model Registry.
Capability support
Capability | Support | Maturity |
Discovery of agents | No — models only | — |
Model import | Yes | GA |
Manual agent registration | No — not in the Register Agent list | — |
Trace ingestion | Yes | GA |
| Yes | GA |
| Not selectable | — |
Note: There is no manual-registration route for this platform, and that is deliberate rather than a gap. Assets arrive through the connection — models by import. If you need a record for something this connection does not return, register it against the framework it is actually built on, or use the OpenTelemetry route. See Bring Your Own Agent.
Before you begin
Create the connection first — Discovery sweeps a connection your tenant already holds. It does not collect credentials. See Create a Connection.
Know which account or environment you are scanning — One connection covers one.
Agree the identity's scope — Discovery sees exactly what the connection identity can list — and so does the model import list. A narrow identity produces an inventory that looks complete and is not.
Decide what you actually intend to govern — Because this connection reaches both registries, it is easy to import far more than you use. Import the models that are actually called; an inventory of unused models is noise in every downstream report.
Add the connection
Step 1: Open + Add Application in Discovery
Step 2: Select Core42 Compass
Step 3: Confirm Observe · Advisory
It is preselected and is the only tier available for this platform.
Step 4: Choose the connection and click Connect
Importing models
Separately from the sweep, Model Registry > Add Model > Core42 Compass lets you pick models from a connection and import them. The list is the connection's own answer to what it can serve, so a model missing from it is a scope question rather than a product one.
Full treatment in The Model Library.
Verify
The new row shows PLATFORM as Core42 Compass and STATUS as Connected. DISCOVERED populates once the first sweep completes.
Open the connection to see its Assets table. A sweep returns the models available on your Core42 Compass account — there are no agents to discover. Everything arrives excluded — discovered but not governed — until you register it. See Review & Triage Discovered Assets.
Limitations
Observation only — Controls set to
BlockorMaskcannot take effect on this connection.Flagworks as documented and every violation is recorded as an incident.No manual registration — Assets come from the connection. There is no
Core42 Compassoption inRegister Agent.Coverage stops at the connection's permissions — Assets the identity cannot list will not appear, and their absence is not reported.
Troubleshooting
The sweep completed but DISCOVERED is empty. Either the account genuinely hosts none, or the connection identity cannot list them. Check the second before concluding the first.
The model import list is empty. "This connection returned no importable models" means the connection works and has nothing to offer — a different problem from a connection that fails.
An imported model shows no spans. A model's spans arrive through whatever calls it. Start with the calling agent, not the model. See Model Registry Troubleshooting.
A Block control never blocks. Expected on an advisory connection. See Connection Types.