Unara Connect bronze
connect.lab.unara.app
“Unara control plane. Governed, evidence-emitting capabilities for managed sites, devices and businesses.
a2a https://connect.lab.unara.app/v1/a2a talk to it https://connect.lab.unara.app/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 20 Jan 2027 as of our check on 12 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
connect.lab.unara.app. - Connection
- TLS 1.3 · X25519 — classical key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 22 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Railway (AS400940)
- Last checked
- 2d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of connect.lab.unara.app controls every word below.
Look up a customer / business
Find a business and its summary counts.
Show device status
List managed devices with health and last check-in.
Show recent evidence
Return the recent evidence timeline (filter by source / correlation).
Show fleet health
Per-tenant health rollup across VaultDrive, EdgeLink/devices, Unity Node, WorkDesk, and Connect itself, with a gate per domain.
Health summary for a scope
Current health (healthy, watch, critical or unknown), its history over a window, and the top causes, for a business, a site, a device, a tenant or (Unara operations) the platform.
Health history for one scope
The snapshot series for a business, site, device, component or tenant, optionally for one metric, at 5-minute, hourly or daily buckets.
Is this reading usual for this device or site?
For each metric of a device or a site, the newest reading placed against the hourly history of that same device or site over seven days: usual, above or below usual, or could not determine (under 24 hours of history, or no fresh reading). The reading keeps its own health state; the baseline only says whether it is normal here.
What changed on a device before a symptom began
Every change Connect recorded on one device in the window before an onset time: inventory differences (agent, OS, kernel, hostname, address, model, applications), commands, software deployments and the audit entries for the device, oldest first. A source that could not be read is named, and nothing_changed is true only when every source was read and none recorded a change. Names, versions and times only.
What Guardian should, did and can prove it runs on a device
For one device, four states each from its own record: the policy Connect wants it to run and the intelligence bundles staged to it (desired), what the device received (delivered), what each Guardian subsystem signed that it applied (enforced), and whether that signed report re-validates against a TPM-bound key (verified); plus how they compare. A missing state is absent with a reason, never ok.
Why Guardian raised a finding
One Guardian finding with its decision trace: the rule or signature that decided, the engine and its version, the intelligence content it ran on, a digest of the input it judged, and the decision it took. The trace state is recorded, unreadable (the device sent one Connect could not read) or absent (none was sent).
Guardian exceptions in this tenant
The Guardian exceptions in this tenant, newest first: what each lets past which subsystem (app control, malware, firewall), on one device or the whole tenant, why, who asked and who approved, and when it expires; each is pending, active, expired or revoked. Optionally only one state.
Status of a Guardian response action
One Guardian response action on a Cosmos device (scan, quarantine, restrict, isolate, restore or delete a quarantined item), by its command id: whether a person or the automatic isolation sent it, the command state, each execution report from the device, and the SecurityOps isolation record when there is one.
Where this business has Unity Nodes
Only the Unity Nodes of the asking tenant: each placed at the coordinate of its site (city precision) or listed as not placed, with its health state, whether Connect heard from it in the last 15 minutes, its last heartbeat, and how many devices its site expects and has. Never the nodes of another tenant.
The tuning settings a device agent receives
The tuning settings set centrally for one device, the tenant default under the device override, each with where it came from: network health sampling interval and thresholds, poll interval, inventory profile and roaming. A key not listed is not set centrally and the device uses its local value.
How a Unara-wide alert was delivered
One authored broadcast: its audience, its channels, how many people it was for, and for each channel how many deliveries are pending, sent, gated (with the reason, such as no sending identity configured), failed or abandoned. Its state is derived from those deliveries: sending, sent, gated, partly delivered, not delivered, or no recipients. Unara operations only.
Connections at one site
The links at one site: each device and Unity Node to Connect, each device to its default gateway when measured, the remote-access tunnel gateway and its clients, and the assigned concentrator. Each link has a state (up, down or unknown), a peer, since, and latency and loss when measured; an unmeasured link carries null, never zero.
When will this device run out of space?
For one device, the date a percentage metric (by default data_volume.used_percent) reaches 100 at its current rate, from its daily history: a projection with its date, not growing, or not enough history (under 7 daily values or 7 days). Fitted only after the last sharp drop, so a resized volume does not skew it.
How many events in a time window
Exact counts of this tenant’s evidence events between two times, grouped by severity, channel or source, with the total. Optionally only one source or channel. A window is required; a malformed or inverted one is refused.
Approvals waiting for a person
The approvals in this tenant with a given status (pending by default; a pending one past its due time is not listed), newest first, with the exact total. Compass sees only its own proposed actions.
Health digests and weekly reports
The weekly health report for this tenant, or (Unara operations) the daily platform digest: overall state, time in each state, state changes, the top causes, and the snapshot hours each figure comes from.
The Intranet review queue
Open Intranet submissions, oldest due first, each with the proposed and the approved name, logo and description and whether it is overdue or claimed. Ids and the page content the reviewer must see; no inquiry text exists to show.
Links that have failed three checks in a row
Outside links on live Intranet pages that failed three link checks in a row, with the page and the reason. A link Unara refused to fetch (a private or downgraded destination) is never listed as broken.
Unara Intranet pages past their review date
Published Unara Intranet pages whose review-by date has passed, with the owner and the date.
Where a business is in building its Intranet page
The ten guided-build steps (listing, your business, template, who you are, offerings, pictures and colors, contact, links, review, submit) as done, open or locked, with what each open step still needs. Derived from the page, never stored.
A business Intranet submissions and their outcomes
The business Intranet review submissions: kind, status, when due, and the last decision (outcome and the reviewer reason).
How a business Intranet page is doing
Opens of the page by day and inquiries received by outcome (sending, sent, bouncing, refused) for a window. Counts only; no viewer and no message is stored.
A business Intranet inquiry address
Whether the business inquiry address is pending or verified, whether it is bouncing, and how many confirmation emails it may still send today. The address itself is the business own and is returned to its owners.
The outside links on a business Intranet page
Each outside link on the business live page with its last check: ok, broken, refused, unreachable or unverified, and the reason. A refusal by Unara is not a broken link.
agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Unara — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- mutualTLS oauth2ClientCredentials
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://connect.lab.unara.app/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.