One catalog,
wired to your stack,
automated end to end

This guide is for the people who keep the lights on — cataloging what's running, wiring Ethira into the stack you already operate, and automating the parts that shouldn't need a human.

Read it in any order. Where something's quicker from a terminal or a script than a screen, this guide says so — and the Agent can do a lot of it for you in plain language.

Your asset catalog

Inventory is your single, workspace-wide catalog of everything IT — and every asset can link to the risks and vendors it touches, so governance runs end to end.

Each asset type has its own tab, and they all work the same way: create a record, open it to edit and add relationships, and search or filter to find what you need. Here's what you can track:

• Systems & productsYour IT systems and software, with dependencies and ownership.
• MicroservicesA service catalog — purpose, stack, and relationships.
• RepositoriesCode repos with their linked systems, teams, and security config.
• DatasetsData assets with classification, ownership, and processing context.
• AgentsAI agents running in your infrastructure (register them here first).
• Devices & locationsServers and equipment, plus the sites they live in.

The Overview tab draws a relationship graph across everything, so dependencies are easy to see. There's also a Vendors view that shows your third parties as inventory — with a clear split between direct vendors and their subcontractors.

People & teams

People and teams are the thread that ties ownership together — across assets, risks, and access reviews.

Under Inventory → People you'll find everyone with their roles, team memberships, the assets they own, and related risks. Teams works the same way — create a team, add members, and link the assets they operate. People records feed access-review lists and risk ownership, so keeping them current pays off everywhere else.

Sync from Google Workspace

Rather than maintain people by hand, connect Google Workspace at the organization level and Ethira syncs your directory — users and group memberships — into people records automatically. Set it up under My Organization → Integrations. The same connection also powers vendor discovery elsewhere in Ethira.

API & CLI access

Everything you can do in the UI, you can drive from your own tooling — CI/CD pipelines, scripts, and scheduled jobs.

API keys

Create scoped keys under Settings → API Keys. Give each one a name and an optional role so you're granting least privilege, and copy the token when it's shown — you only see it once. Keys belong to the workspace, not the person who made them, so they keep working when someone leaves the team, and you can disable any key from the same page when you rotate or retire an integration.

The Ethira CLI

The CLI is your command-line path for inventory sync, vendor operations, and CI gates — ideal when shadow tooling never touches a browser. Grab the setup steps from the in-product Ethira CLI tab, authenticate with an API key, and you've got commands for the things you do most:

• Sync your inventoryPush systems, microservices, datasets, repositories, teams, and devices — individually or all at once.
• Work with vendorsList and operate on vendor records straight from a script.
• Gate your pipelinesRun a quick connection or status check as part of CI.

Authenticate however suits your setup — an environment variable, a config file, or a flag on the command.

Connect AI tools (MCP)

Ethira speaks MCP in both directions, which trips people up — so here's the clear version. It comes down to which way the data flows.

Read access comes on by default for connected servers; turn on write tools deliberately, when you mean to. A token's reach always matches the permissions of whoever created it, so scope access with roles. There's also a third piece — a governance registry where developers request MCP servers and admins approve them — covered in the security & IT guide.

Agent telemetry

For the AI agents running in your own code, Ethira can stream what they do — the calls they make, the tools they invoke, the decisions they take — into one place alongside the rest of your inventory.

1. Register the agent under Inventory → Agents so it has a home.
2. Issue an ingest token scoped to that agent.
3. Add the Ethira SDK to your agent's code and point it at the token.

From then on, its activity shows up on the agent's page within seconds — giving you runtime visibility into the AI in your stack, not just a static record that it exists.

Jobs & workflows

Watch what's running

The Jobs page is your window into background work — imports, processing pipelines, and other long-running operations. It auto-refreshes while jobs are active, and you can expand any row to see its steps and progress. It's the first place to look when a vendor import, risk import, or backfill doesn't land as expected.

Put routine work on a schedule

Workflows let you schedule Agent prompts to run on their own — a nightly inventory audit, a weekly monitoring digest, a monthly compliance summary. Create one with a prompt and a schedule (hourly through monthly, or a cron expression), flip it on, and use Run now to test without waiting. Each run opens its own Agent conversation in the history, so you can always read back what it did.

Integrations

Ethira plugs into the stack you already run. Most live under Settings; directory sync sits under My Organization → Integrations.

• Jira & LinearLink risk mitigations to issues, with status sync from Jira.
• SlackNotifications, Agent posting, and discovered-vendor alerts.
• SSO & SCIMSAML sign-on and automated user provisioning.
• Google Drive & Microsoft 365Browse and import documents without re-uploading.
• Google CalendarSync compliance events and review dates.
• VantaCompliance posture and vendor discovery sync.
• Cursor & ClaudeMonitor team AI usage and spend.
• Google WorkspaceDirectory sync into people records.

A quick tip: hit ⌘K or Ctrl K anywhere and type the integration's name to jump straight to its settings.

Get help & what's next

The Agent handles a lot of operational work directly — it knows your inventory and can read and write through the same tools your scripts use. A few prompts that fit: