Frequently asked questions

We are in pre-launch. Early access teams get onboarded in weekly batches, with hands-on onboarding while you port your first pipeline.

Only if you want us to do the collecting. Proxy IP on its own gives you credentials for your own tools; Data Scraping tokens cover crawls we run for you.

Proxy traffic used by our own crawlers is included in the token price. Buy a Proxy IP pack only when you want to route your own tools through our residential pool.

Not necessarily. Proxy IP is the part price data cannot do without — it keeps the series continuous and locally correct, whether you crawl with your own tools or ours.

Data Scraping does the monitoring itself. Proxy IP becomes necessary as soon as the pages you watch differ by country or start throttling repeated visits.

No. Data Scraping alone produces the dataset. LLM Analytics is what turns it into a readable analysis, and Proxy IP matters once the study crosses borders.

You buy a token pack up front and spend it per request. Easy pages cost 1 token, heavily protected ones up to 10 — the cost of every target is shown in the dashboard before you run a job.

Standard packs are transfer-based, in GB, bought as a one-off. Port-based billing is available on custom plans for long-running sessions; the two can be combined on one account.

Transfer packs suit bursty collection: you pay for the gigabytes you move and nothing else. Port-based billing suits long-running sessions at steady throughput, and is available on custom plans.

It stays valid for 30 days from purchase, and packs stack on the same balance. You can top up at any time from the dashboard.

Monitoring only means something as a trend. A year of comparable measurements is the smallest unit that shows whether your visibility is moving.

By how much work the page takes: a static HTML page is 1 token, a JavaScript-rendered page around 3, and a heavily protected one up to 10. The score for every target is shown before you run the job.

They stay valid for 12 months from purchase. You can top up at any time and packs stack on the same balance.

Either. A token pack covers a single study; re-running the same scope each quarter turns it into a trend without new setup.

The job pauses rather than failing: completed requests are kept and the remaining queue waits. Top the balance up from the dashboard and it resumes from where it stopped. Usage alerts can warn you at 80% of a pack so it does not happen unnoticed.

It depends on the pack. Scraping token packs stay valid for 12 months from purchase; proxy transfer packs are valid for 30 days. The exact validity is shown on every plan in the pricing table, and new packs stack on the same balance.

In the billing section of the dashboard, including past invoices and the pack balance. Write to sales only if something needs correcting on a document.

Yes. Residential exits are selectable by country and region, and routing retries automatically inside the same geo when a request fails.

Country on every pack, region-level targeting from Growth up. Retries stay inside the geography you asked for, so a run of results remains comparable.

Yes. Each market is its own scope, collected through local exits so assortment and prices reflect what a buyer there sees.

Yes, on Scale and Custom packs. Send us the target and the fields you need; we maintain the parser as the site changes.

Any public listing page: your competitors’ own shops and the marketplaces they sell on. You supply the URLs or categories; we handle rendering, retries and the schema per source.

Yes. Promo flags, bundle indicators and loyalty prices are captured as separate fields, so a median can be built on shelf price alone or on the effective price.

As fresh as the schedule you set: daily is typical for a large catalogue, hourly for a short list of key SKUs. Each run reports what changed, so alerts fire on movement rather than on every crawl.

Anything you choose to watch: price, availability, title, description, images, badges, review count, or position on a category or search page. Each run is compared against the previous one.

As often as the pack allows — hourly for a short list of key listings, daily for a full catalogue. Cadence is set per source, so critical shops can run more often than the rest.

Yes — marketplace listings, category pages and search results, per market. Ranking and buy-box changes are tracked alongside the product data.

Usually yes. Send us the target URL and the timestamps, and we adjust rendering, pacing and exit selection for that source. On Scale and Custom packs we maintain the parser for you as the site changes.

Write to support with the target list and the throughput you need. Limits exist to protect both our infrastructure and the sources, so we raise them where the pattern of use permits — usually within a day.

No. Scraping and proxies work standalone. LLM analytics sits on top when you want classification, sentiment or written summaries instead of raw rows.

A defined set of category prompts is put to the model on schedule. We record whether your brand appears, in what position, how it is described, and which sources the answer leaned on.

The major commercial assistants, selected per scope. Multi market covers three models in parallel; Portfolio covers the full set.

We build the set from the category and the market, then you confirm or edit it. Custom sets are available on Portfolio.

Indirectly — the source breakdown shows which pages shape the answer, which is where content and PR work pays off. We report; we do not manipulate model output.

Whatever the question needs: assortment and attributes per competitor, price levels, review volume and sentiment, and category structure — collected from the sources that define the category.

LLM Analytics reads the collected reviews and returns structured output: themes, complaints, praised attributes and their frequency, each traceable back to the source.

Yes. Sub-users get their own credentials, quota and geo rules, and the dashboard reports transfer per sub-user.

Yes — sub-users get their own credentials, quota and geo rules, and the dashboard reports consumption per sub-user. Ask support if you want the structure set up with you.

We collect publicly available data, respect robots directives you configure, and sign a DPA. SSO, audit logs and SOC 2 work are part of the Enterprise track.

We collect publicly available data, honour the robots directives you configure per source, and sign a DPA. Audit logs and SSO are part of the Custom track.

In the dashboard, and wherever else you need it: REST API, webhook per run, or scheduled exports into a warehouse. Most teams push it straight into the pricing engine.

Yes. Every run can fire a webhook, so changes land in Slack, in a queue or in your own tooling. The dashboard keeps the full history either way.