Surface companies showing buying intent, then reach the right person at each one.
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.
One key and one wallet. Call company.signals, contact.find, contact.verify as canonical capabilities with stable schemas; the router picks the provider on evidence and every run shows provider, latency, quote and charge.
| Capability | Description | Providers |
|---|---|---|
| company.signals | Hiring, funding, expansion and news signals for a company. | |
| contact.find | Find a professional email from a person and company. | |
| contact.verify | Verify deliverability and status of a professional email. | |
curl https://api.routergrowth.com/v1/run \ -H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \ -d '{ "capability": "company.signals", "input": { "domain": "..." }, "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.