Skip to main content
The collector receives events from the SDK and gateway, deduplicates them into AI assets, and serves the Registry API. You run it yourself.
There is no hosted collector endpoint yet. Every example in this section assumes a collector you operate, typically at http://localhost:8000.

What you get

pgvector is not optional — the registry’s semantic search builds an HNSW index over asset metadata, so a stock PostgreSQL image will not work.

Prerequisites

  • Docker and Docker Compose
  • Python 3.11 or later

Bring it up

1

Clone the repository

2

Start PostgreSQL with pgvector

3

Install the Python packages

4

Run the migrations

5

Seed demo data (optional)

Useful for seeing a populated registry before you have real traffic.
6

Start the collector

7

Run the end-to-end demo

The PYTHONPATH prefix is required because the collector and the shared db package are separate distributions in one repository.

Authentication

Requests carry a tenant API key as a bearer token:
A missing or unrecognised key returns 401 with an RFC 7807 problem-detail body. Tenant resolution happens on every request, so isolation is enforced server-side rather than by client-supplied tenant IDs.
Run the collector on a trusted network. Key handling is still being hardened, so treat the current build as suitable for evaluation and internal pilots — not for exposure on the public internet. Put it behind your VPN or private network, and don’t terminate it on a public load balancer yet.

Verifying it works

Running the tests