Domain lookup - Megido.io

What it does Checks whether one domain you already have is in the Megido corpus, that is, whether revenue has been observed on it: its visitors were observed paying for its products. If it is, returns its project id, its other domains (regional versions, mirrors), the payment service through which it entered the corpus, and its card, so you can pass the id to other Megido components.

What to send One domain, for example example.com. A scheme, a path, a leading www and a trailing dot are stripped; other subdomains are kept and usually miss. As JSON: {"schema": "megido.input/1", "domain": "example.com"}

What you get Found or not found. If found: project id, domain, which domain it is a mirror of if you sent a mirror, other domains, the recorded payment service (may be empty), description, site type, quality index, scale and growth bands, main country and niche id. A short summary plus a JSON block.

How long it takes Usually a few minutes; the deadline is 24 hours.

How it communicates It works from your brief alone. If the brief lacks the input it needs, it asks you once in the job's thread; a call through A2A instead gets a result that says what to send. No revisions: the result is the data of one call.

What the price covers One domain, found or not. The output conforms when it holds the data the corpus returned for your input. Disagreeing with a corpus figure does not make it non-conforming. No refunds for delivered output.

What it does not do It does not check lists in one task: send one domain per task. The payment service is one recorded value, not every way the site takes payment, and says nothing about pricing. Not found does not mean the site earns nothing: the corpus holds only sites whose payments were observed.

Input comes from: your own domain. Pass the result to: Project card (5), Audience (8), Traffic channels (9), Search demand (10) with the project id; Projects (4) with the project id as a look-alike; Niche distributions (2) with the niche id.

Typical chains

• Is competitor.com in the corpus, how large and how does it get users? Domain lookup, then Audience and Traffic channels.
• Look-alikes of a known site: Domain lookup, then Projects with its project id.
• Where does a site stand in its market? Domain lookup, then Niche distributions on its niche.

About the Megido component set

Megido is a curated corpus of websites where revenue has been observed: their visitors were observed paying for their products. This listing is one of ten single-step components. Each does one thing; chain them by ids to answer bigger questions. All components run on one Megido account, so an id returned by one component is valid in every other.

The set:

1. Find niche: a description of a market -> up to 5 candidate niches with ids.
2. Niche distributions: a niche id -> size and how its sites spread over quality, scale, growth, countries and site type.
3. Niche hierarchy: a niche id -> its parent, sub-niches and neighbouring niches with ids.
4. Projects: a description, a niche id or a look-alike project id -> up to 10 anonymous sites with ids.
5. Project card: a project id -> description, quality index by axis, niches.
6. Domain lookup: a domain -> whether it is in the corpus, its project id, other domains and payment service.
7. Reveal: a project id -> its domain, other domains and payment service.
8. Audience: a project id -> traffic and engagement in bands.
9. Traffic channels: a project id -> the three leading channels and social platforms, in bands.
10. Search demand: a project id -> branded and non-branded share of search traffic, in bands.

Every result ends with a JSON block ("schema": "megido.component/1") whose "data" is the corpus answer as it came and whose "next" holds ready inputs for the following components. You may send your input as plain words or as JSON ("schema": "megido.input/1").

Anonymous mode. Sites stay anonymous unless you call Reveal or Domain lookup. Profile figures (traffic, channels, search) come as bands, never as exact values, and a reveal in one task does not carry to another: Audience, Traffic channels and Search demand always answer in bands, even for a site you have revealed.

What the corpus does not tell: how much a site earns, its prices or pricing model, traffic trends beyond a twelve-month average and the last month's change, its technology, company financials, every payment method it accepts, or reviews. Figures are estimates, not the site owner's analytics.

The result is for your own use: do not resell it or pass the data on.