Emergency Reporting
Emergency Reporting (ESO) scores 2/100 on xpay's Agent-Ready Index v2: partial pricing visibility.
Emergency Reporting (ESO) pricing
Sales-led pricing
This is a sales-only model. The page contains no pricing tiers, rates, or self-serve purchase options. The entire page is a lead-capture form requesting organization details to schedule a sales call. No pricing information is publicly disclosed.
How Emergency Reporting scores on the agent-ready dimensions
Public pricing visibility
2 / 15
Self-serve checkout
0 / 15
Public API + docs
0 / 20
Usage-based / metered pricing
0 / 20
Free entry path
0 / 7
No sales call required
0 / 7
Card / wallet / x402 payment
0 / 6
Machine-readable bonus (MCP / OpenAPI)
0 / 10
Total
2 / 100
Six-step check: can an agent actually buy from Emergency Reporting?
Discover price
Select a plan
Pay per task
Avoid a sales call
API docs without auth
Estimate cost upfront
Pros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-06. 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.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- All advertised tiers route to a sales contact form; an agent cannot complete a purchase autonomously.
- API documentation is gated or absent; an agent cannot inspect the integration surface without authentication.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
- The pricing URL did not render numeric tier data on the scoring date — possibly a router or sales-led landing page.
How Emergency Reporting 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 | false |
| headline_phrasing | Get Started — Built by data. Driven by outcomes. is now part of |
| tier_count | 0 |
| 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 | https://emergencyreporting.com/api-development-for-organizations/ |
| api_docs_auth_walled | false |
| 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":true,"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 Emergency Medical Services stack up.
Compare the agent-ready picks in Emergency Medical Services.
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 picksEmergency Reporting
2
/ 100 (rubric v2.0)Emergency Medical Services
Get Started — Built by data. Driven by outcomes. is now part of
0
No
Sales-led
0 / 1
Public
No
Not published
2026-05-08
Sales-led pricing
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 Emergency Reporting with peers
Highest-scoring companies in the same category that an AI agent might evaluate as an alternative.iOps360
42
NEMT Cloud Dispatch
42
AdvanceDispatch
17
APSS Rescue
9
Phoenix EMS
9
CentralSquare CAD
4
AMBFlight
4
TripSpark NEMT
4
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.