AgentInfra Radar
Data dictionary

Every lead field is designed to make public-source research easier to review

The lead format is intentionally simple: enough structure for scoring and segmentation, enough context for a human to verify before outreach.

projectName
The public project, product, company, framework, or repository name.
  • Used for deduping and quick scanning.
  • May be normalized when a repo and product use different names.
website
The official website, docs site, launch page, or primary product page.
  • Public pages are preferred over third-party profiles.
  • Broken or unclear sites are flagged for review.
githubUrl
The GitHub repository or organization URL when a meaningful public repo exists.
  • Used for activity, release, and community signals.
  • Not required for closed-source companies.
category
The working market category used for routing the lead to the right buyer.
  • Examples: MCP server, AI agent tool, LLM gateway, observability, security, evals.
  • Categories can change after manual review.
growthSignal
A concise summary of public activity that makes the project worth watching.
  • Examples include launch activity, changelog velocity, GitHub movement, community adoption, integrations, or hiring signals.
  • It is a research signal, not a guaranteed buying event.
possibleNeed
A reason the team may eventually need a product or service from an AI infrastructure vendor.
  • Examples: security review, gateway controls, observability, evals, deployment help.
  • This is a hypothesis to verify before outreach.
leadScore
A practical priority score for review and outreach planning.
  • Higher scores reflect category fit, freshness, source confidence, and actionability.
  • Scores are not predictions of revenue or response rates.
contactAngle
A context-aware outreach angle that explains why this lead is relevant.
  • Designed to reduce generic cold outreach.
  • The sender should still personalize and verify before contacting.
source
The public source or source type that produced the lead.
  • Examples: GitHub, official docs, product site, MCP directory, launch post, company page.
  • Private inboxes and scraped personal data are not used.
verificationStatus
The current review state of the lead.
  • Examples: public-source verified, needs manual review, monitor only.
  • Used to decide whether a lead is ready for export or should stay in the watchlist.
Next step

See these fields in context

The sample page shows how the fields appear in a real beta lead table.

Open sample leads