Google Trends Opportunity Briefing Agent avatar

Google Trends Opportunity Briefing Agent

Pricing

from $5.00 / 1,000 useful opportunity briefs

Go to Apify Store
Google Trends Opportunity Briefing Agent

Google Trends Opportunity Briefing Agent

Turn public Google Trends Trending Now RSS signals into source-linked, AI-ready opportunity briefs with predictable useful-result pricing.

Pricing

from $5.00 / 1,000 useful opportunity briefs

Rating

0.0

(0)

Developer

jack su

jack su

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

Turn public Google Trends Trending Now RSS signals into compact, source-linked opportunity briefs for AI agents and research workflows.

The Actor does not use undocumented private APIs, does not promise exact search volumes, and treats trends as current attention signals rather than predictions or factual proof.

Input

{
"geo": "US",
"focusTerms": ["artificial intelligence", "small business"],
"maxBriefs": 3,
"requestTimeoutSecs": 20
}

Input notes:

  • geo: two-letter Google Trends region code.
  • focusTerms: optional phrases used to prioritize relevant trends.
  • maxBriefs: defaults to 3 to keep first-run cost predictable. Increase it when you want a broader briefing.

Output

Each useful record includes a trend title, related queries, approximate traffic text when available, public source links, matched focus terms, a deterministic opportunity angle, evidence count, completeness score, and observation time.

Pricing

This Actor uses Apify pay-per-event pricing.

  • apify-actor-start: $0.00005 once per run.
  • useful-opportunity-brief: $0.005 per evidence-complete opportunity brief.
  • With the default maxBriefs: 3, a clean run can charge up to three useful brief events plus the small start event.
  • Failed, incomplete, duplicate, and diagnostic records do not trigger useful-opportunity-brief.
  • apify-default-dataset-item is intentionally not configured.

Safety

  • Uses only public RSS data.
  • Preserves source URLs and observation timestamps.
  • Does not infer sensitive traits or target private individuals.
  • Uses certificate verification, public-host restrictions, size limits, and request timeouts.