Signal Six

Every 90-day competitive report generated for this company, newest first. Use get_report to read one.

list_reports

Your own company and the competitors you track, each labelled, never hidden: whether it is mapped yet, its profile as it states it on LinkedIn, what the map holds for it, how many of its pages we have read and when, and how many signals we have scored for it. Start here: the other map tools take these names.

list_companies

Dated changes to what the companies show on their pages, newest first: something added, changed (before → after, in words), or no longer shown. Each carries the company's words, the page and the date, and the signal our judges scored on that same page state, or a note saying why there is none. History goes back 12 months. A change is counted only when an earlier stored state of the same page did not show it, so a fact that was already there when we started reading is not reported as new. Dates are when we stored the page state that first showed the change, not when the company made it.

list_changes

Features as each company names them: the product that has it, the plans that include it (included, limited, add-on, or listed as not included), and the shared capabilities we file it under so companies can be compared. The capability is our reading; the feature and its plans are the company's words.

list_features

Products, services and plans, one row each, with the role it is sold in, its stage when the company states one, the markets it competes in, and its pricing inline. A plan is a tier or a paid add-on tier; a product priced on its own is a product.

list_offerings

One row per priced product, service or plan: the price points as the company writes them (amount, per what unit, per what period, currency), its terms (billing, minimum, contract, trial), whether it is contact-sales, and the previous price when it changed. Prices are never converted: a per-seat price and a flat price are not comparable without a seat count, so compare units before you compare amounts.

list_pricing

Markets the companies compete in and industries they serve or belong to, with which of your companies is in each, and whether the company says so ("stated by the company") or it is our reading of its pages.

list_markets

Customers each company names publicly: how it shows them (a logo, a case study, a testimonial, an announcement), the result it claims for them, the quoted person's role, the product they use when stated, and their industry. shared: only customers more than one of your companies names.

list_customers

Search the competitor signals Signal Six has scored for this company: launches, pricing changes, feature releases, positioning shifts. Each signal carries the importance our judges gave it and a one-line read of why it matters to this reader. Use get_signal for the full source text of one of them, get_signals to read up to 25 in one call, and get_signal_facets to ask how the matching set breaks down before you page through it. This returns ONE PAGE, not the whole match. Newest first, `limit` rows from `offset` (default 50 from 0, max 200). `total` is how many signals match your filters, `hasMore` says whether any were left out, and `nextOffset` is the offset for the next page. A busy company produces thousands of signals a quarter, so 50 rows can cover two days: read `total` before you describe the period, and walk `nextOffset` until `hasMore` is false if you need the whole window. Size the call to your client's tool-result limit: a full 200-row page is roughly 100KB. Stay at 50 unless you narrow the row with `fields`, which returns `id` plus only the fields you name — `["competitor", "importance", "headline"]` is about a fifth the size, and enough to pick which signals to read in full. Filters, all optional and combined with AND: `competitorId` is a rival uuid from get_profile. `family` is one of content, offering, company, other — the first half of the signal's category. `category` is the whole label, one of content/thought_leadership, content/research, content/event, content/case_study, content/recognition, offering/launch, offering/feature, offering/pricing, company/ownership, company/funding, company/partnership, company/people, company/positioning, other/uncategorized, for when the family is too coarse. `minImportance` keeps that rung and stronger on the scale noise < minor < major < critical. `from` and `to` are ISO-8601 timestamps bounding when we observed the signal, `from` inclusive and `to` exclusive. `q` is a case-insensitive substring matched against the headline, our why line and the stored page text — it is not semantic search, so prefer a filter over a guessed keyword. IMPORTANCE FLOOR: `minImportance` defaults to "minor", so the `noise` rung is left out unless you ask for it by name. Most of what we observe is noise — a rotated reCAPTCHA token, a CDN swap, a rival posting about somebody else — and it is scored so we can exclude it. Pass `minImportance: "noise"` only to audit our scoring, never to survey what a competitor did.

search_signals

Rewrite the company's profile: their role, company, and the strategic context every alert and report is written through. Defaults to a dry run that returns the diff and says what saving costs. Only call it with dry_run false after the reader has seen that diff and agreed to it in this conversation. Saving deletes every scored signal for the company and re-scores them under the new profile.

update_profile