ContactOut
ContactOut's pricing URL resolves, but plan structure is not surfaced clearly enough for an agent to enumerate without hand-parsing. No per-unit price was found on the page; an agent has no direct way to estimate the cost of a single task. All advertised paths route to a sales conversation rather than a self-serve checkout. No public API documentation URL was discovered.
Pricing
Contact sales
How ContactOut scores on the agent-ready dimensions
Public pricing
10 / 15
Usage-based / metered
0 / 25
Self-serve checkout
0 / 15
Public API
0 / 15
Low / no minimum
0 / 10
Unauth automated payment
0 / 10
Bonus (machine-readable pricing)On top of /100 base
0 / 5
Total
10 / 100
Six-step check: can an agent actually buy from ContactOut?
Discover price
https://contactout.com/pricing — $25 / $49 visibleSelect a plan
https://contactout.com/pricing — four tiers distinguishablePay per task
https://contactout.com/pricing — quota-based, no $/call rateAvoid a sales call
https://contactout.com/pricing — Team/API tier requires sales contactAPI docs without auth
https://contactout.com/api — referenced from sales-only tierEstimate cost upfront
https://contactout.com/pricing — exports/month given but per-export $ not derivedPros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-04. Not a review of the product — only of its current pricing posture for agent buyers.- Pricing is publicly visible on an indexable page — agents can read tiers without scraping past auth.
- API documentation is reachable without a login — discovery and integration can happen in one session.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- Some tiers are sales-led; the highest-capacity surfaces are not self-serve.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
- A unit price is published but consumption per task is not declared upfront — cost predictability is partial.
How ContactOut could lift its score
Add a per-unit price (e.g. $X / 1K calls) to the pricing page so an agent can compute its own cost before committing.
| pricing_visible | true |
| headline_phrasing | Pricing |
| tier_count | 1 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | null |
| per_unit_price | null |
| annual_required | false |
| self_serve_paid_tiers | 0 |
| sales_only_tiers | 1 |
| public_api_docs_url | null |
| api_docs_auth_walled | null |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
| per_unit_classification | null |
| usage_headline_present | false |
| custom_tier_present | false |
| agent_friendly | {"ai_pricing_json":false,"agents_txt":false,"llms_txt":false,"sitemap_xml":false,"mcp_server_card":false,"agent_skills_index":false,"x402_supported":false} |
View raw extracted page text →
Claim this scorecard & lift your score.
Get the breakdown of every signal we measured, the one-line fix, and how your peers in Enrichment APIs stack up.
Compare the agent-ready picks in Enrichment APIs.
If you're building or running an AI agent that needs to buy from this category, see who's scoring highest right now.
See agent-ready picksContactOut
10
/ 100 (rubric v1.1)Enrichment APIs
Pricing
1
No
Sales-led
0 / 1
Auth-walled
No
Not published
2026-05-04
Discovery files and protocols
Side-channel signals — informational, not part of the score. Each protocol is independent; adoption signals the publisher is thinking about agent buyers.ai-pricing.json
agents.txt
llms.txt
sitemap.xml
MCP Server Card
Agent Skills
x402 / MPP
Compare ContactOut with peers
Highest-scoring companies in the same category that an AI agent might evaluate as an alternative.People Data Labs
71
Snov.io
70
Hunter
62
RocketReach
60
Apollo.io
36
Lusha
32
ZoomInfo
18
FullContact
8
Explore the Agent-Ready SaaS Index
25,480+ SaaS scored on agent-buyability — browse by readiness band, category, or jump straight to a pay-per-run tool on xpay.tools.