Invented specifics
Addresses, opening hours and prices arrive fully formed and completely unsourced. They read exactly like the ones that are true.
Verifiable venue intelligence
Ask an assistant where to eat and it will answer with total confidence: an address that moved two years ago, a price nobody quoted, a rating nobody gave. Power Scraping is the opposite bargain. You collect the posts you are entitled to collect; we enrich them and hand back records in which every single field cites the evidence it came from. What we cannot evidence, we return as unknown.
Collect with your own Instagram account, in your own browser, with the Power Scraping Collector extension (desktop Chrome, Edge or Brave). We never see your Instagram password.
The problem
A language model asked to summarise a venue will produce a fluent answer whether or not the facts exist. There is no marker on the output that separates "the creator said this" from "this seemed plausible". If you are publishing a guide, briefing a client or feeding a recommendation engine, that difference is the whole job.
Addresses, opening hours and prices arrive fully formed and completely unsourced. They read exactly like the ones that are true.
A throwaway comment becomes "widely praised". A single visit becomes a rating. The chain back to who actually said it is gone by the time you see the summary.
When a client challenges one field, you have to re-do the research to answer. There is nothing to point at, which means there is nothing to defend.
The answer
The engine is the boring part. The product is the audit trail it leaves behind.
You name each profile as an authorized target and state the basis: your own account, a signed creator contract, a documented client mandate, or public-interest research — plus a reference we can audit. Nothing runs against an undeclared handle.
The Power Scraping Collector runs in your own browser, under your own Instagram login. It sends us a fixed list of fields from the declared profile's posts — never comments, your feed, your messages or who you follow. Captions and post details become numbered evidence items. Enrichment then proposes fields — venue, city, prices named, sentiment, experience tags — and each proposal must point at evidence ids.
Any field whose citations do not resolve is dropped, not downgraded. Every job records what was collected, when, and under which declared authorization basis.
A real record
This is the shape of what the API and the MCP connector return, abridged to the fields that matter here. Note the last row: the creator never gave a rating, so the field is null and says so.
rec_8d31f0a4 · from a single Instagram postmid_range| Field | Value | Evidence | Quoted from the source |
|---|---|---|---|
venue.name |
Trattoria da Oscar | Caption ev_01 |
"finally back at @trattoriadaoscar for the cotoletta" |
location.city |
Milan | Geotag ev_02 |
"Milano, Lombardia" |
price.mentions_eur |
14, 22 | Caption ev_03 |
"cotoletta €22, calice di rosso €14, worth every cent" |
assessment.sentiment |
positive | Caption ev_03 |
"worth every cent" |
venue.place_id |
null | none | No places provider is asked to match the venue, so no third-party place id is attached; the venue is named from the post's own location tag and caption. |
assessment.explicit_rating |
null | none | No rating appears anywhere in the post, so the field is returned as unknown rather than inferred from tone. |
An enrichment pass that cites an evidence id which does not resolve has its whole field discarded before the record is written. There is no "low confidence" tier that lets an ungrounded guess through.
Compliance posture
Collection happens on your own device, under your own Instagram account, and only when you start it. We enrich, meter, store and export what your Collector sends. The limits are product features rather than promises, enforced in the extension and in the API.
A job runs only for a profile declared as an authorized target, with an authorization basis and an auditable reference; a job for an undeclared or revoked handle is refused. Posts of any other account are dropped on your device and again on our server.
An Instagram warning, a challenge or a logout ends the job. The Collector does not spoof device fingerprints, solve challenges or rotate proxies. It has no cookies permission and never reads cookies, and your Instagram password and session never leave your browser — we never receive, store or replay them.
Every collection job writes an audit event naming the actor, the target and the declared basis. Every job needs your click to start, and acceptance of the current acceptable-use version is required before any job will run at all.
We delete a target's data on request, keep records only for your plan's retention window, and never pool, sell or re-sell them.
Pricing
One metered unit: a post the service actually processed. No seat games, no per-field charges, and jobs stop at the allowance. Every plan collects through the Power Scraping Collector in your own browser.
Free
Prove the evidence trail on a handful of posts before you commit.
Most popular
£20 /month
No VAT charged
For one operator running continuous venue intelligence.
£800 /month
No VAT charged
For teams collecting on behalf of named clients.
Questions
A pointer from one field of a record to one numbered evidence item collected from the source, together with the modality (caption, location label, venue lookup), a short verbatim excerpt, the method that produced the field and its confidence. You can quote it straight back to whoever is challenging the field.
Nothing gets written. A field whose citations do not resolve against the collected evidence is discarded atomically before the record is stored. The record still arrives, with that field null rather than filled in.
Ones you are entitled to have collected: your own accounts, creators you hold a signed contract with, clients who have given you a documented mandate, or subjects of public-interest research. You declare the basis and a reference per target, and you revoke it the moment it stops being true.
Yes: the Power Scraping Collector extension, on desktop Chrome, Edge or Brave. You pair it with your account using a short single-use code from the dashboard. Collection then runs in your browser, from your own device and network, under your own Instagram login. We never see your Instagram password, and the extension has no cookies permission and never reads cookies. Phones, Safari and Firefox cannot collect; any browser can read and download results.
A fixed list of fields from the declared profile's posts: post id, handle, link, dates, caption, location label, media type, links to the media, and like and comment counts. Never comments, other page text, your feed, your messages or who you follow. Posts of any other account are dropped on your device and again on our server.
Yes, it can. In manual mode, the default, you open posts yourself and press Send this post. Automatic mode is off until you turn it on in a browser and acknowledge the risk: it then opens the profile and its posts in a visible tab at a slow, fixed pace with small daily caps. Instagram may still treat automated activity as a breach of its terms and respond with warnings, temporary action blocks or restrictions on your account — that risk is yours, not ours. The Collector stops at the first warning, challenge or logout; a challenge pauses that browser for 24 hours and switches automatic mode off until you turn it back on. You must follow Instagram's terms and have a lawful basis for every profile you collect.
The job stops and says why. We do not evade access controls of any kind, and we will not add that capability. A refusal you can see beats data you cannot explain.
Connect Power Scraping to Claude, ChatGPT or an IDE agent and the same evidence-grounded records become callable in a conversation: list targets, start a collection, poll it, then read records and search them. The assistant quotes the citations instead of inventing the gaps. Collecting from a chat still needs the Collector paired on a desktop browser. See the quickstart.
One post your Collector sent and the service enriched in the current billing period. Posts skipped by a filter are not metered, and downloading results you already have never counts again.
Yes. Every finished job has Download CSV and
Download JSONL buttons in the dashboard, and the same files come from
GET /v1/jobs/{job_id}/export in the REST API — every record, with its
evidence citations intact.
No card. Install the Collector, declare one target, run one collection, and read the evidence behind every field it returns.