Introducing market intelligence: app stores, marketplaces, and review data

Today we're launching the market-intelligence stack — /app-data, /ecommerce, and /business. App store rankings, marketplace product and pricing data, and reviews across Google, Trustpilot, and TripAdvisor — all as structured data your agent can query through the same key it uses for everything else. This is the layer that lets an autonomous company understand the market it's competing in.

The problem: market data lives behind a hundred scrapers

An agent running a real business needs to know things that don't live in a single API:

• How does our app rank against competitors, and what are reviewers complaining about?
• What does this product sell for across Amazon and Google Shopping, and who's underpricing us?
• What's our rating on Trustpilot, and is it trending the wrong way?

The status quo is a graveyard of brittle scrapers and one-off integrations — each store and review site with its own structure, rate limits, and ways to break. It's the kind of plumbing that's never quite done and never quite trustworthy, and it's completely impractical for an agent to assemble on the fly. The data exists; the access doesn't. Until now.

What's in the stack

Three primitives, each covering a slice of the market, all behind your Naïve key:

• /app-data — Google Play and App Store rankings, reviews, ratings, and metadata.
• /ecommerce — Amazon and Google Shopping product details, pricing, and sellers.
• /business — Google Business, Trustpilot, and TripAdvisor reviews and ratings, plus travel and place data.

They follow a passthrough model that mirrors each provider's structure. Most operations use an async task pattern: POST a task, then GET the result by id (or poll tasks-ready) once it's processed. A few high-frequency lookups have a live variant that returns inline.

App store intelligence with /app-data

App-store endpoints submit a task on POST, then return the result on GET .../:id:

# Submit an App Store reviews task
curl -X POST https://api.usenaive.ai/v1/app-data/apple/app-reviews \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "app_id": "123456789", "location_code": 2840 }'
 
# Submit a Google Play app-info task
curl -X POST https://api.usenaive.ai/v1/app-data/google/app-info \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "app_id": "com.example.app" }'
 
# Retrieve a finished task by id
curl https://api.usenaive.ai/v1/app-data/apple/app-reviews/<task_id> \
  -H "Authorization: Bearer $NAIVE_API_KEY"

Marketplace data with /ecommerce

Amazon and Google Shopping use explicit /task submission plus /task/:id retrieval:

# Submit an Amazon products task
curl -X POST https://api.usenaive.ai/v1/ecommerce/amazon/products/task \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "wireless earbuds", "location_code": 2840 }'
 
# Submit a Google Shopping products task
curl -X POST https://api.usenaive.ai/v1/ecommerce/google/products/task \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "standing desk", "location_code": 2840 }'
 
# Retrieve the result once ready
curl https://api.usenaive.ai/v1/ecommerce/amazon/products/task/<task_id> \
  -H "Authorization: Bearer $NAIVE_API_KEY"

Reviews and reputation with /business

Trustpilot and TripAdvisor are task-based; some Google Business endpoints (like my-business-info) also offer a live variant:

# Submit a Trustpilot reviews task
curl -X POST https://api.usenaive.ai/v1/business/trustpilot/reviews/task \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "domain": "example.com" }'
 
# Submit a Google Business reviews task
curl -X POST https://api.usenaive.ai/v1/business/google/reviews/task \
  -H "Authorization: Bearer $NAIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "Blue Bottle Coffee" }'

Each endpoint returns structured records — ratings, counts, prices, rankings — designed for comparison and monitoring, not prose. Most return a task you retrieve by id; the live variants return inline.

What you can build with market intelligence

Run continuous competitive monitoring — Schedule /cron jobs that pull competitor app rankings, marketplace prices, and review sentiment on a cadence, and alert when something shifts.

Build a dynamic pricing agent — Pull current Amazon and Google Shopping prices for your SKUs and competitors, decide a new price, and write it back to your store — the read side of an autonomous pricing loop.

Watch your reputation across every surface — Aggregate Trustpilot, Google, and app-store reviews into one rolling reputation score, and trigger a response workflow when ratings dip.

Validate a market before you enter it — Before /formation spins up a company, an Employee sizes demand and competition with market data plus /seo — research that's structured, not guessed.

Feed decisions, not just dashboards — Combine market data with /research so the CEO agent reasons over both hard metrics and synthesized context before acting.

Get started

Drop this starter prompt into any coding agent to wire up Naïve:

Read https://usenaive.ai/skill.md and use it to set up Naïve in my project.

• App data: usenaive.ai/docs/getting-started/app-data
• E-commerce: usenaive.ai/docs/getting-started/ecommerce
• Reviews: usenaive.ai/docs/getting-started/reviews
• Pair with SEO: usenaive.ai/docs/getting-started/seo
• Quickstart: usenaive.ai/docs/getting-started/quickstart
• Join the community on Discord