Knowledge Base
API referenceOpen app
KB-204Updated October 15, 2026

Context: identity and competitors

The page where you tell the platform who you are. Everything it writes is shaped by what's here.

Video walkthroughSpeed

Context in the header (pinned by default). Two sections: Identity and Competitors.

Identity

Everything your company is, on one long page. Jump to a section in the toolbar moves you between the sub-sections, in this order:

  • Manifesto: who you are, in your words. What you build, who you serve, what you stand for.
  • Stances: what you believe and argue for. Every draft is written from them.
  • How AI describes you: Name to feature in content, In one line, who are you?, What you ARE, Ways to describe you (up to three), What you are NOT, and Default framing. This is the factual guardrail every mention the platform publishes is held to. When it was drafted from your site during setup, confirm it before relying on it.
  • Main targets to rank for: phrases you want to be THE answer for, company-wide or per offering. Each scope holds up to five active targets by default. Suggest proposes them from your evidence; Add target takes your own. Each collection's Control Room shows which pillars steer toward them.
  • Priority topics: what you lead with right now. Headlines that match get a scoring boost.
  • Market & mentions: Target market, the country whose search demand you're measured against (each collection can pick its own), and Where you're mentioned, a read-only list of every place your published posts name you, by collection.
  • Offerings: each product you'd name on its own. An offering stores only what differs from the company, and collections that publish it inherit through it.
  • Sources: notes, links and documents that correct the rest (below).

Manifesto and Stances save as you type. Below the page, the Positioning assistant takes a description of your company, or proposes stances from your existing content; it answers with Proposed changes, and nothing is saved until you press Apply. Version history keeps every version; restore an earlier one from there.

Competitors

  • Tracked competitors: name, domain, and aliases. Suggest competitors finds them from your domain and positioning; Suggest aliases fills in the other names they go by.
  • For each, a stance: Never mention (stripped from every post) or Neutral (may be named factually, with your brand named favorably alongside).
  • From AI answers: pending review: brands the model named in your AI answers. Accept one to track it.
  • Keep-out rules: holds Topics to Avoid, a hard filter on headline candidates.

Sources

Part of Identity. Feed the platform notes, links, and documents about your company and it proposes corrections. Paste Notes, add up to ten Links (a Notion page, a Google Doc, anything public), or upload Documents (PDF, DOCX, TXT, or MD, up to 10MB each), then press Analyze context. The Proposed changes are grouped by where they land: Positioning, Competitors, Identity, Voice (the writing kernel), and Visuals (the brand look). Mark each Accepted or Rejected, confirm you've reviewed them all, and apply; nothing is saved automatically. Earlier runs stay under Past context passes.

Cadence

Cadence isn't on Context. Each collection's publishing pace is shown on Activity and set per collection (or with set_collection_config over the API).

Topic clusters

Clusters are not on Context. A blog's coverage areas, topical map, and series live on its own Topics tab in the Control Room (KB-202), because the ground a site covers belongs to the site.

Over the API

get_company_info / set_company_info (name, domain, manifesto, market), get_positioning / set_positioning (priority topics, stances, avoid topics), suggest_positioning (a draft, unsaved), suggest_onboarding (a whole starting strategy from just your domain: description, positioning, and ranking targets, nothing saved until you apply it), list_competitors / add_competitor, add_ranking_target, ingest_context { text, links } / apply_context { ingestion_id, accepted_change_ids } (the two steps of Sources), get_brand_context / import_brand_context { domain } (the imported brand profile the visuals draw from), import_sitemap.

Related