Skip to main content
Human guide: work with your agent → Inspect one ScrapeCreators action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use ScrapeCreators for public social evidence that a web search can miss. Examples include Reddit comments, TikTok videos and comments, Instagram Reels, and YouTube transcripts or search. For local-business contact recovery, consider ScrapeCreators when a verified Facebook or Instagram identity is available. It can supplement sparse Maps or website data. Keep Maps and website extraction as the first pass. Do not require social recovery in every SMB workflow. Test a small sample before large or uncertain recovery work. A small supplied Play needs no additional pilot or repeated approval. Inspecting results does not authorize paid recovery or repair. Good candidate tools:
  • scrapecreators_facebook_profile: public Facebook page/profile About data, including business email/phone/address/website when available.
  • scrapecreators_facebook_profile_posts: recent post text, useful when the About block lacks an email but posts mention catering, reservations, bookings, or contact details.
  • scrapecreators_instagram_profile: public Instagram profile bio/contact fields, including business public email/contact button/website when available.
  • scrapecreators_instagram_user_posts: post/caption text, useful when the bio links to booking, menu, or contact pages.
Profile and contact actions are research candidates. An installed SDK can still categorize them differently. If a category-filtered search misses them, try an unfiltered ScrapeCreators search:
For SMB email recovery, verify at least two identity attributes before accepting social profile data. Use business name, address, phone, website/menu/booking link, or Google Maps profile. Retain the source platform, profile URL, extracted contact field, timestamp, and identity evidence for review. Pricing note: Deepline credit pricing for these endpoints is generated from the provider pricing metadata and rendered on the public provider pages.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.