---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "orabot"
kind: "agentic_registry"
operator: "Ora"
researched_at: "2026-10-23"
confidence: "high"
json_url: "https://newruntime.com/readers/orabot.json"
canonical_url: "https://newruntime.com/readers/orabot/"
---

# OraBot

> Ora's on-demand scanner that scores how ready a website is for AI agents. When someone requests a score for a domain it fetches robots.txt, llms.txt, OpenAPI specs, MCP manifests, structured data and /.well-known/poppy.json in a bounded burst; during a scan it also requests the homepage under other crawlers' UAs (GPTBot, ClaudeBot, PerplexityBot).

## Dossier

- Kind: Agentic web & MCP registries
- Operator: Ora (https://ora.ai/)
- Documentation: https://ora.ai/bot
- robots.txt tokens: none documented
- Feeds: monitoring
- Respects robots.txt: Not documented. Docs list robots.txt among fetched files but do not say whether its rules are honored; opt-out via Ora Studio or hello@ora.ai. Web Bot Auth signing (keys at /.well-known/http-message-signatures-directory) is planned, not live.
- Verification: No published method
- Labels matched in our logs: orabot

## Why it matters to New Runtime (our interpretation)

A visit means someone requested an agent-readiness score for our domain, i.e. our machine-facing surfaces (llms.txt, MCP, OpenAPI) are being evaluated.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 164 requests on 1 days; first seen 2026-09-11, last seen 2026-09-11; Dormant.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- https://ora.ai/bot

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md