Build intelligence
MI source labels
Entity, events, signals, and topics saved on Market Intelligence sources.
On a Market Intelligence source, labels describe what you are watching — not what Aevico has already detected in articles. They are stored as JSON on the source row and travel with that connector in the console and API.
Saved as labels on this source. On ingest, Aevico matches these as keywords (title, summary, body), lists hits under Signals, can fire Alerts (MI detection), and can gate Workflows IF on mi_detection fields. That is substring matching — not LLM classification.
Fields
| Label | Meaning |
|---|---|
| Entity name | Who or what this source is about (e.g. Acme Corp, EU cloud market). |
| Entity type | Optional: company, organization, person, product, market, or industry. |
| Events to watch | Business events you care about (funding, hiring, regulation, …). Checkboxes on the form. |
| Signals to watch | Derived patterns you want flagged later (buying signal, threat, market trend, …). |
| Topics / keywords | Free-form subjects, comma-separated, for search and future matching. |
Defaults by capability
When you change capability on a new MI source, events and signals prefill from the table below. You can add or remove checkboxes before save.
| Capability | Default events | Default signals |
|---|---|---|
| Lead Intelligence | Funding, Hiring, Expansion, Product launch, Partnership, Procurement | Buying signal, Growth signal, Opportunity |
| Competitive Intelligence | Product launch, Pricing change, Acquisition, Partnership, Hiring, Leadership change | Competitive signal, Threat, Opportunity |
| Company Intelligence | Funding, Acquisition, Expansion, Hiring, Leadership change, Product launch | Growth signal, Business change |
| Industry Intelligence | Funding, Product launch, Acquisition, Regulation, Partnership | Market trend, Growth signal, Emerging technology |
| Government Intelligence | Regulation, Tender, RFP, Contract award, Government announcement | Regulatory risk, Procurement opportunity, Policy change |
| Sales Intelligence | Product launch, Funding, Pricing change, Regulation, Demand / market change | Market opportunity, Market risk, Emerging trend |
JSON shape
{
"entity_name": "Acme Corp",
"entity_type": "company",
"events": ["funding", "hiring"],
"signals": ["buying_signal", "growth_signal"],
"topics": ["cloud", "security"]
}Bulk import
Console → Sources → Import accepts the same object on each source row in a sources array. Omit intelligence_metadata to prefill events and signals from the capability default table.
{"sources":[{"source_type":"rss","source_url":"https://…","category":"mi-company","intelligence_metadata":{"entity_name":"Acme Corp","entity_type":"company","events":["funding"],"signals":["growth_signal"],"topics":["cloud"]}}]}Console API
POST /v1/console/sources and PUT /v1/console/sources/{id} accept optional intelligence_metadata as a JSON object on the request body (same shape as above). The field is stored on the source; pollers do not use it yet.
Editing capability
On a new MI source, changing capability replaces the event and signal checkboxes with that use case’s defaults. When editing an existing source, changing capability keeps your saved checkboxes unless you clear them first.
What works today
- Save and edit labels on Add/Edit source.
- Ingest, full-text search, Feed API, and item counts per capability.
- Keyword substring matching of labels against ingested items — listed under Console → Signals.
- Keyword and category alerts on ingested items.
- Workflows triggered on item.created.
Not live yet
- LLM / NLP classification into event or signal types.
- Workflows triggered from Signals detections (use Alerts → MI detection or Workflows IF mi_detection today).
- A BI/analytics dashboard for MI.
The second list is intentional — detection and Automate are the product path, not charts.
- Market Intelligence use cases
- SignalsFuture detection layer.
- IntelligenceConceptual roadmap.
34 articles on this site. Engineering notes on GitHub.