ReadableByAI
Menu ▾

DATA PARTNERSHIPS · DESIGN-PARTNER STAGE

License evidence about how AI crawlers reach the web.

ReadableByAI is building a consented crawler-intelligence panel: verified AI-crawler demand, access reliability, spoofing outcomes, status classes, route categories, and latency bands across monitored domains. We are speaking with data and product teams before fixing the first production feed.

Review the schema and current coverage

Early coverage is limited and selected, so every discussion starts with the actual domain count, active history, verification mix, and cohort gaps. No buyer receives a reliability claim that the panel cannot support.

Prefer email? alex+data@midnightdev.dev

Useful for

  • AI-search, SEO, and digital-intelligence platforms
  • Bot management, fraud, WAF, and infrastructure products
  • Research and measurement teams tracking agentic web activity
  • OEM products that need a governed crawler-access benchmark

What the contributed record contains

  • Normalized crawler vendor and bot token
  • Vendor-network verdict: verified, impostor, or unknown
  • Route category rather than exact path
  • Status class rather than response body
  • Latency band when available
  • Timestamp rounded to the hour
  • Coverage, methodology, and cohort metadata

The source is free hosted monitoring used under versioned Data Contribution Terms. Domain authority is required at setup.

What is never part of the commercial product

  • Original Vercel or CDN log batches
  • Client or visitor IP addresses
  • Exact paths, query strings, cookies, referrers, or headers
  • Raw user-agent strings or customer credentials
  • PostHog tokens or drain secrets
  • Public domain-level rows or small identifiable cohorts

“Minimized” does not mean anonymous: the internal contributed record includes the monitored domain. Public and multi-buyer outputs will use aggregation, cohort suppression, and coverage disclosure. Private domain-level access would require a separate agreement and rights review.

How the first partnership works

  1. Review the data dictionary and live coverage note.
  2. Choose one buyer question the panel can answer honestly.
  3. Agree on cohorts, suppression, refresh, delivery, and permitted use.
  4. Run a time-boxed private design-partner feed before any marketplace listing.

Planned delivery options include scheduled files, API access, or a private cloud share. The production method will be selected with the first paid design partners; it is not represented as live today.