Skip to content

Engineer & Integrations Path ​

Connect the systems that matter so governance work is grounded in real artifacts: repositories, docs, tickets, and operational signals.

Outcome ​

You leave this path with:

  • Scout Connectors connected for user-scoped research
  • AI System Sources configured for stable access and testing
  • API tokens and Modulos Client set up when you need push-style integration

Time to first value: 30–90 minutes
Prerequisites: you have access to the AI System and permission to configure integrations. Each Source type and each Connector type is off until an Organization Admin turns it on in Organization → Source & Connectors.

Path at a glance ​

  1. Connect Scout Add user-scoped Connectors for docs, code, and tickets.
  2. Add AI System Sources Configure service accounts for stable AI System access.
  3. Set up API access Create API tokens and validate authentication.
  4. Validate signals Confirm Scout and Runtime Inspection can retrieve the right context.

Step 1: Connect Scout Connectors ​

Goal: let Scout retrieve external context within a user permission boundary.

Where in Modulos

  • User Settings → Connectors (visible only when chat/Scout is enabled for your organization)

Do this

  • Connect the systems you expect Scout to reference, such as GitHub, Bitbucket, Atlassian, or Google Drive.
  • Confirm the Connector shows the status Active.

You’re done when

  • Scout can reference external context you have access to

Step 2: Add AI System Sources ​

Goal: configure stable service accounts attached to the AI System for automation and signals.

Where in Modulos

  • AI System → Settings → Sources (AI System Owners and the organization roles with full access to AI Systems)

Do this

  • Add metrics-capable Sources for Runtime Inspection (for example Prometheus, Datadog, Langfuse, AWS, or Vijil).
  • Add context Sources that Scout can read (for example GitHub or Azure) when relevant.
  • You do not add Modulos Client: it is a built-in row in the Sources list, and your code pushes metrics to it.

You’re done when

  • Sources are configured and visible in AI System Settings

Step 3: Set up API tokens and Modulos Client ​

Goal: enable push-style integrations and automation.

Where in Modulos

  • User Settings → API Tokens to create tokens
  • See Modulos Client for client usage and examples

Do this

  • Create a token for your integration use case and store it securely.
  • Use Modulos Client when you want your code to push metrics or artifacts into Modulos.

You’re done when

  • you can authenticate to the API and perform the intended integration workflow

Step 4: Validate end-to-end behavior ​

Goal: confirm connected systems produce usable governance context.

Where in Modulos

  • AI System → Runtime Inspection to validate metrics, tests, and results
  • The Scout chat panel, opened with the Scout button in the page header, to validate retrieval and grounded answers

Do this

  • Create or update a test condition and run it.
  • Ask Scout a question that requires external context and confirm it returns grounded references.
  • If you see access issues, confirm Connector permissions and Source configuration.

You’re done when

  • runtime inspection signals are visible and Scout can retrieve the expected context

Next handoff ​