# Seyn

> Official documentation for Seyn: the knowledge extraction engine.

## Docs

- [Add a memory](https://docs.seynlabs.com/api-reference/add-memory.md): Teach Seyn something in plain language.
- [Create a custom source](https://docs.seynlabs.com/api-reference/create-source.md): Register a source for any system Seyn has no prebuilt connector for.
- [Get ingestion batch status](https://docs.seynlabs.com/api-reference/get-ingest-batch.md): Poll a batch you submitted to /v1/ingest.
- [Get a knowledge library](https://docs.seynlabs.com/api-reference/get-library.md): Detail for a single knowledge library version.
- [Get memory status](https://docs.seynlabs.com/api-reference/get-memory.md): Poll a memory you submitted to /v1/knowledge/memory.
- [Get a process rule](https://docs.seynlabs.com/api-reference/get-rule.md): Full detail for a single rule, including its structured condition.
- [Get the provenance chain for a rule](https://docs.seynlabs.com/api-reference/get-rule-provenance.md): The full four-hop audit chain from a rule back to source records.
- [Ingest records](https://docs.seynlabs.com/api-reference/ingest-records.md): Push a batch of records from any system into Seyn.
- [Create a custom source](https://docs.seynlabs.com/api-reference/ingestion/create-a-custom-source.md): Register a custom source to ingest data from any system Seyn has no prebuilt connector for. Returns a `sourceId` you then push records to via `POST /v1/ingest`.
- [Get ingestion batch status](https://docs.seynlabs.com/api-reference/ingestion/get-ingestion-batch-status.md): Poll the status of an ingestion batch. Normalization runs asynchronously, so a batch moves `queued` → `processing` → `done` (or `error`). Counts reflect what landed: `recordsCreated` after dedup, `eventsCreated` after normalization.
- [Ingest records](https://docs.seynlabs.com/api-reference/ingestion/ingest-records.md): Push a batch of records to a source. Each record is stored verbatim and deduplicated by content hash (re-sending an unchanged record is a no-op), then normalized into events asynchronously. Reuse a record's `recordId` on update and Seyn supersedes the prior version instead of duplicating it.
- [List sources](https://docs.seynlabs.com/api-reference/ingestion/list-sources.md): List every data source in your organization, both prebuilt connectors and custom sources you created.
- [Add a memory](https://docs.seynlabs.com/api-reference/knowledge/add-a-memory.md): Teach Seyn something in plain language. Send a sentence or paragraph describing what you want the knowledge base to know ("deals over $50M always need board sign-off, not just the CEO"), and Seyn processes it into structured knowledge: it extracts the claims, reconciles them against what it already…
- [Get memory status](https://docs.seynlabs.com/api-reference/knowledge/get-memory-status.md): Poll a submitted memory. Processing moves `queued` → `processing` → `applied` (or `error`). Once applied, `summary` explains what Seyn understood and the counts report how many assertions it created or superseded.
- [Search knowledge](https://docs.seynlabs.com/api-reference/knowledge/search-knowledge.md): Run a natural-language query over the organization's knowledge base. Returns ranked rule hits.
- [Get a knowledge library](https://docs.seynlabs.com/api-reference/libraries/get-a-knowledge-library.md)
- [List knowledge libraries](https://docs.seynlabs.com/api-reference/libraries/list-knowledge-libraries.md)
- [List rules in a library](https://docs.seynlabs.com/api-reference/libraries/list-rules-in-a-library.md)
- [List knowledge libraries](https://docs.seynlabs.com/api-reference/list-libraries.md): Versioned snapshots of your organization's extracted knowledge.
- [List rules in a library](https://docs.seynlabs.com/api-reference/list-library-rules.md): Process rules scoped to one knowledge library version.
- [List process rules](https://docs.seynlabs.com/api-reference/list-rules.md): Paginated list of process rules in your organization.
- [List sources](https://docs.seynlabs.com/api-reference/list-sources.md): Every data source in your organization, prebuilt and custom.
- [Aggregate pipeline metrics](https://docs.seynlabs.com/api-reference/pattern-metrics.md): SQL-computed analytics over your event data, for BI tools and dashboards.
- [Aggregate pipeline metrics](https://docs.seynlabs.com/api-reference/patterns/aggregate-pipeline-metrics.md)
- [Get a process rule](https://docs.seynlabs.com/api-reference/rules/get-a-process-rule.md)
- [Get the provenance chain for a rule](https://docs.seynlabs.com/api-reference/rules/get-the-provenance-chain-for-a-rule.md): Returns the full audit chain: rule → inference log (the LLM call that produced the rule) → normalized events the LLM observed → raw records ingested from source systems.
- [List process rules](https://docs.seynlabs.com/api-reference/rules/list-process-rules.md)
- [Search knowledge](https://docs.seynlabs.com/api-reference/search-knowledge.md): Run a natural-language query over your extracted knowledge.
- [Authentication](https://docs.seynlabs.com/authentication.md): How API keys work, how to manage them, and how to debug auth errors.
- [Core Concepts](https://docs.seynlabs.com/core-concepts.md): The vocabulary that shows up in every Seyn surface: dashboard, chat, API, and these docs.
- [Introduction](https://docs.seynlabs.com/introduction.md): Seyn observes how your organisation actually works and turns it into structured, versioned, fully auditable knowledge.
- [Architecture](https://docs.seynlabs.com/platform/architecture.md): The five-layer system model, the write path vs. the read path, and the debugging order that explains most surprises.
- [Chat](https://docs.seynlabs.com/platform/chat.md): Conversational access to extracted knowledge: streaming answers with citations that resolve all the way down to source records.
- [Connectors](https://docs.seynlabs.com/platform/connectors.md): Anything that can produce records can feed Seyn: the connector contract, building your own, and the prebuilt catalog.
- [Dashboard](https://docs.seynlabs.com/platform/dashboard.md): A tour of the web app: what client teams see, and the operational surfaces that run the machine.
- [Documents](https://docs.seynlabs.com/platform/documents.md): How Seyn turns folders of DOCX, PDF, and XLSX files, and the folder structure itself, into structured, attributed events.
- [Events](https://docs.seynlabs.com/platform/events.md): How heterogeneous raw activity becomes one common event schema, and how the same human gets one identity across every system.
- [Knowledge](https://docs.seynlabs.com/platform/knowledge.md): The assertion substrate, the rules and libraries projected from it, and the staged extraction that produces them from your events.
- [MCP Server](https://docs.seynlabs.com/platform/mcp.md): Knowledge tools over the Model Context Protocol: give any MCP-capable agent grounded, org-scoped, fully audited access to extracted knowledge.
- [Multi-tenancy & Roles](https://docs.seynlabs.com/platform/multi-tenancy.md): How organisations are isolated, how the three-tier role model works, and the one invariant that even superadmins can't cross.
- [Observability](https://docs.seynlabs.com/platform/observability.md): One central inference function, versioned prompts, and self-hosted tracing: how every LLM call stays accountable.
- [Provenance](https://docs.seynlabs.com/platform/provenance.md): Every claim Seyn makes traces back four hops to raw source data, and the database makes breaking that chain impossible.
- [Query](https://docs.seynlabs.com/platform/query.md): The hybrid pipeline behind every question: expanded queries, up to five rank signals fused, cross-encoder reranked, graph-expanded, with an explain mode that shows its work.
- [Security & Trust](https://docs.seynlabs.com/platform/security.md): How credentials are handled, what defends the ingestion surface, where your data goes during LLM analysis, and what we rate-limit.
- [Quickstart](https://docs.seynlabs.com/quickstart.md): From zero to a real response in under 10 minutes.
- [SDK Reference](https://docs.seynlabs.com/sdk-reference.md): Every SDK method with TypeScript signatures, example responses, and the Python equivalents.
- [Status](https://docs.seynlabs.com/status.md): What's in testing and what's planned. With reasons, not badges.

## OpenAPI Specs

- [openapi](https://docs.seynlabs.com/openapi.yaml)