Ashby vs Greenhouse for AI agents
Greenhouse is more ready for AI agents than Ashby: 63 vs 56 out of 100. Greenhouse is ahead on semantic HTML, named buttons and links and labelled form fields. Ashby is ahead on markdown docs.
What an agent finds
| Ashby | Greenhouse | |
|---|---|---|
| Score | 56/100 | 63/100 |
| Blocks AI agents | No | No |
| robots.txt disallows | No AI bots | No AI bots |
| llms.txt | At the root | At the root |
| Remote MCP server | none found | none found |
| Docs MCP server | none found | none found |
| OpenAPI spec | none found | none found |
| Developer docs | developers.ashbyhq.com/ | developers.greenhouse.io/ |
| Public pricing | www.ashbyhq.com/pricing | www.greenhouse.com/pricing |
| Self-serve sign-up | No self-serve page we could open | No self-serve page we could open |
Check by check
60 core points every site needs, plus 40 split between letting an agent sign a team up and connecting through the API. Sign-up and API checks count half each.
| Check | Points | Ashby | Greenhouse |
|---|---|---|---|
| Core | 48 | 58 | |
| Agents get the real page, not a bot wall | 12 | ✓ | ✓ |
| robots.txt lets user-triggered agents in | 6 | ✓ | ✓ |
| Answer-engine crawlers are allowed | 4 | ✓ | ✓ |
| Content is in the raw HTML | 6 | ✓ | ✓ |
| Semantic HTML (main, nav, header) | 4 | · | ✓ |
| Icon buttons and links have names | 3 | · | ✓ |
| Form fields have labels | 3 | · | ✓ |
| Images have alt text | 3 | ✓ | ✓ |
| The page has an H1 | 2 | ✓ | ✓ |
| Structured data (JSON-LD) | 5 | ✓ | ✓ |
| Meta description and Open Graph tags | 3 | ✓ | ✓ |
| sitemap.xml | 3 | ✓ | ✓ |
| llms.txt | 4 | ✓ | ✓ |
| Dates show the content is fresh | 2 | · | · |
| Sign-up | 5 | 5 | |
| Public pricing page | 5 | ✓ | ✓ |
| A self-serve sign-up link | 4 | · | · |
| Sign-up page opens for agents | 3 | · | · |
| A free plan or trial | 3 | · | · |
| No card needed to start | 2 | · | · |
| SoftwareApplication data | 3 | · | · |
| API | 2.5 | 0 | |
| OpenAPI spec | 3.5 | · | · |
| Remote MCP server | 4 | · | · |
| Docs as markdown | 2.5 | ✓ | · |
| Self-serve API keys | 3 | · | · |
| OAuth client self-registration | 2.5 | · | · |
| OAuth discovery metadata | 1.5 | · | · |
| SDKs and a CLI | 1.5 | · | · |
| Free tier or test keys | 1.5 | · | · |
Automated, read-only scan of each homepage, robots.txt, llms.txt, docs, OpenAPI paths and MCP endpoints on 3 Nov 2026. How scoring works.
Check them again today
Sites change. Run the live scan for the current result, or check your own site.
Questions
Is Ashby or Greenhouse better for AI agents?
Greenhouse is more ready for AI agents than Ashby: 63 vs 56 out of 100. Greenhouse is ahead on semantic HTML, named buttons and links and labelled form fields. Ashby is ahead on markdown docs. Scores are from our scan on 3 Nov 2026.
Does Ashby have an MCP server?
Not one we could find. On 3 Nov 2026 our scan found no remote MCP server for Ashby at the usual addresses (mcp.ashbyhq.com/mcp, api.ashbyhq.com/mcp, the docs host, or any MCP URL linked from its homepage or llms.txt).
Does Greenhouse have an MCP server?
Not one we could find. On 3 Nov 2026 our scan found no remote MCP server for Greenhouse at the usual addresses (mcp.greenhouse.com/mcp, api.greenhouse.com/mcp, the docs host, or any MCP URL linked from its homepage or llms.txt).
Does Ashby block AI agents?
No. Ashby served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.
Does Greenhouse block AI agents?
No. Greenhouse served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.