Competitor ad intelligence
See which creatives competitors run across public ad libraries.
The fragmented way
Separate vendor accounts and API keys for each data source, different auth schemes and response formats, per-seat subscriptions your agent uses a fraction of, and glue code that breaks whenever one vendor changes.
With RouterGrowth
One key and one wallet. Call ads.search, social.posts as canonical capabilities with stable schemas; the router picks the provider on evidence and every run shows provider, latency, quote and charge.
Capabilities used
| Capability | Description | Providers |
|---|---|---|
| ads.search | Public ad-library creatives run by a company or page. |    |
| social.posts | Recent public posts for a social handle. |  |
Copy-paste starting point
curl https://api.routergrowth.com/v1/run \ -H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \ -d '{ "capability": "ads.search", "input": { "query": "..." }, "routing": {"provider": "auto", "strategy": "best_value"} }'
Pricing: the maximum cost is quoted and reserved before the call; failed or unmatched calls are released, with any disclosed exceptions shown by /v1/inspect. Reliability: measured provider success rates will be published once minimum sample sizes are reached; examples on this page are labeled and simulated until then. Limitations: capabilities marked coming soon are not yet executable.