WinLayer documentation
WinLayer is a growth operating system for US federal contractors. It connects supported federal sources into a knowledge graph, identifies potential opportunities before solicitation, scores them against your company profile, and prepares cited decision briefs. Coverage and prediction quality depend on the available source evidence.
The core loop. Signals are ingested from federal sources → normalized into one signal plane → scored against your profile (fit + win probability) → connected in the knowledge graph → surfaced on your Radar with cited AI briefs → tracked through your pipeline to outcomes.
Beta status. Source categories describe supported product paths, not a promise that every feed is healthy or complete in your workspace. Fit and PWin are preliminary decision aids; check their source coverage, evidence, and gaps before committing to a pursuit.
New to WinLayer? Follow Your first 30 minutes. It explains what to click, what each decision means, and what a useful first session should produce.
QuickstartFrom sign-up to a tuned radar in about a minute.Your first 30 minutesA plain-English walkthrough from company setup to the first pursuit decision.ArchitectureThe whole system in one diagram — sources, signal plane, engines, surfaces.Scoring modelExactly how fit and win probability are computed — every point explained.Intelligence suiteContacts, vehicles, protests, agency profiles, and the knowledge graph.Public REST APIPull your scored opportunities and pipeline into any system.Connect AI with MCPGive compatible AI clients a scoped, governed WinLayer toolset.WebhooksSigned events pushed to your endpoints, with verification code.Security & tenancyIsolation by construction, audit trail, credential handling.Integration guidesFirst API call, a webhook receiver, and CRM sync — step by step.The recompete playbookPhase-by-phase capture strategy, mapped to the product.GovCon glossaryFederal-contracting terms and WinLayer decisions in plain language.ChangelogWhat shipped, when — most recent first.
How these docs are organized
- Product — what each surface does and the model behind it: concepts, scoring, the workspace, intelligence, AI grounding, data sources.
- API — the developer platform: authentication, endpoints, rate limits, errors, and webhooks.
- Guides — outcome-focused walkthroughs for a first pursuit, profile tuning, recompetes, and integrations.
- Platform — security, tenancy, roles, and answers to common questions.