Knowledge sources: what Oetzi knows about your company

A post is only as specific as what the writer knows. Oetzi keeps a store of what it knows about your company beyond the conversations it listens to: facts you tell it, what the news and the research say about your category, and what happened in your own tools this week. Every draft, every trend pick and every answer reads that store first. The store and its feeds are free, and connecting your own tools is part of the plan.

Where does the knowledge come from?

Three places. You can type a fact on the Brain Sources tab (a number, a customer story, a thing about the product), and it never expires. A feed runs on a schedule: a news search that keeps what it finds every day, or a source from Alexandria, Firecrawl's library of research papers, developer documentation, government records, finance data, podcasts and ninety more providers. And your own stack: connect GitHub, Stripe, HubSpot, Intercom, Slack, Linear or Google Analytics through Pipedream and events land as they happen.

What does Oetzi do with it?

Four things, all automatic. The daily trend scan treats what your sources learned in the last two days as candidates next to the market's news, so your own release competes for the day's pick on the same page. A feed can carry a rule that turns an item into a pinned topic: a GitHub release, a customer milestone, a deal won. Every drafting run gets a "what we know" block, the five closest items with dates, and the drafter is told to lean on a fact only where it makes the post stronger and never to invent numbers around it. And Ask, on the Trending page, reads the store next to the conversations so a read can cite what you know.

Why one store and not a database per project?

Because every reader asks the same question: what do we know that is close to this, and how fresh is it. A fact stays fresh forever, a document for a month, an event or a metric for days. Ranking is closeness times freshness, one query, and "which feed wrote this" is a column you can filter on. A store per initiative would multiply the plumbing without changing a single answer.

What is a feed?

A saved question with a cadence, or a connected event stream. Pull feeds run every hour on their own clock: hourly, daily or weekly. Push feeds write the moment the event happens. Each feed shows its state, its last run and what it produced on the Brain Sources tab, and pauses itself after three failed runs so a broken source never fills the store with errors.

What does it cost?

The store, the feeds, news searches, your stack's events and polls, Alexandria discovery and search_knowledge are free, with a cap of thirty feed runs a day. An Alexandria tool whose provider lists a price above ten cents a call is one credit a run, refunded when nothing comes back. Connecting your stack needs the $49 plan, because each connected workspace is a seat Oetzi pays Pipedream for.

Questions

Are my customers' support conversations safe?

They stay in your workspace's store, never enter the shared corpus, and every prompt that reads them is told to paraphrase and never quote a person by name. You can forget any item on the Sources tab.

Can my own agent use the store?

Yes. search_knowledge and add_knowledge are capabilities over MCP, REST and the CLI, so an agent working the workspace can ask what you know about churn in September and get rows with dates and sources.