# Avoma, Inc.: 21 point Door Gap
- Site: avoma.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: b2b_saas
- Report: https://www.seconddoor.io/r/avoma-qyqdgs
- Scanner version: 12
Avoma publishes pricing and allows agent access, but offers no API documentation or programmatic onboarding path.
## Scores
| Measure | Score |
| --- | --- |
| Humans | 77/100 |
| Agents | 56/100 |
| Composite | 67/100 |
| Door Gap | 21 points |
| Percentile | 67th |
The human score is the mean of the four human dimensions, the agent score the mean of the six agent dimensions, and the Door Gap the difference between them.
## What the machine actually did
The agent got through 9 of 15 requests, but could not find a contact route for machines. It came up empty on 5 other checks too.
- ok      reach the site at all
- ok      find out whether machines are welcome
- ok      ask whether the door opens for requests carrying the AI crawlers' names
- ok      read the site's own guide for language models
- ok      find out what pages exist
- missing find a contact route for machines
- missing find a published agent interface
- missing find an agent plugin manifest
- missing find out whether verified agents are recognised
- ok      read the homepage as data rather than as a page
- missing find a machine readable API spec
- missing read the developer documentation
- ok      read the prices without running JavaScript
- ok      find a comparison page worth citing
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **No security.txt is published, leaving no machine-readable security contact or incident response policy.** (machine_fetchable_trust)
2. **No API documentation is linked or discoverable, blocking programmatic access entirely.** (programmatic_onboarding)
3. **No MCP manifest is published, preventing Claude and other MCP-aware agents from discovering and using the API.** (agent_aware_instrumentation)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/avoma-qyqdgs
## Files generated from this scan
- **Machine interfaces: where you stand** at `notes`, 10 minutes, no developer needed. Verify: The next scan finds the interface you published answering at its well-known path, and that check passes.
- **pricing.md** at `/pricing.md`, 20 minutes, no developer needed. Verify: The next scan fetches /pricing.md as text and records pricing as machine readable.
- **security.txt** at `/.well-known/security.txt`, 10 minutes, no developer needed. Verify: The next scan fetches /.well-known/security.txt as text and the security.txt check passes.
Each file is written from what this scan found on the site. The content is in the JSON once the evidence is opened: https://www.seconddoor.io/api/reports/avoma-qyqdgs
## The agent door
- **machine_discoverability** 100/100. Robots.txt explicitly names and allows gptbot, a real browser is served normally, key pages render without JavaScript, and a sitemap lists 662 URLs. The homepage carries 6 schema.org types including SoftwareApplication with pricing.
- **programmatic_onboarding** 10/100. No API surface was found in the documentation that was linked and fetched.
- **pricing_legibility** 93/100. 79 prices are readable without JavaScript on the pricing page. All tiers are published with no sales gate. Prices are structured as Offer schema with UnitPriceSpecification. Per-seat pricing is clear.
- **agent_aware_instrumentation** 20/100. Robots.txt names 1 AI crawler (gptbot) and allows it, showing awareness. No MCP manifest exists at the 3 standard paths. No ai-plugin.json or Web Bot Auth signals are present.
- **machine_fetchable_trust** 40/100. No security.txt is published at /.well-known/security.txt. The homepage answers automated requests normally. An agent can fetch the site but cannot verify the organization's security contact or incident response policy.
- **commercial_rails** 70/100. Prices are published in raw HTML on the pricing page with no demo gate. A self-serve signup form is 2 steps from the homepage and asks only for email with Google SSO. Offer schema is present.
## The human door
- **steps_to_first_value** 80/100. The primary CTA 'Try Avoma for Free' is 2 steps from the homepage and leads to a signup form. The form itself is 2 steps away. No payment is required to start.
- **required_fields** 98/100. The signup form has 1 field and 0 are required. Google SSO is offered as an alternative. No payment information is requested. A visitor can begin without providing a name, company, or phone number.
- **verification_walls** 80/100. No verification requirement appears on the signup page. Google SSO avoids email verification entirely. The page has inline error containers but no CAPTCHA, SMS, or email confirmation copy is visible.
- **error_recovery** 50/100. The signup form has 1 input and 0 carry validation rules or descriptions. An inline error container is present on the page. If validation fails, the user will see an error, but the form provides no guidance on what input is expected or why.
---
Scored by SecondDoor. Method: https://www.seconddoor.io/methodology
Scan another site: https://www.seconddoor.io
Rate an issue or this report: POST https://www.seconddoor.io/api/feedback, or the rate_fix tool on https://www.seconddoor.io/api/mcp