AI Readiness ·
Free AI Readiness Check
Enter a domain. We read what is public, name the kind of organization behind it, map the systems its data lives in, and check whether AI assistants can read it at all. Then we point at the free next step that fits. Nonprofits, schools, clinics, shops, city teams, startups.
Free, no signup, nothing stored. Public sources only.
Reading the public footprint of
AI Readiness ·
Seven components, published rather than hidden. Change one and rerun the check to watch it move.
AI crawler access, read from your robots.txt
Illustrative time a first AI workflow could return to your team.
Matched against the resources your page loads, your response headers, your cookies, and your Content-Security-Policy.
Strengths, gaps, and the duty of care that comes with them.
Austin AI Hub programs, ranked by fit to what we found. All free, all open to everyone.
Tailored to the kind of work you do.
How people move through the Hub. Most organizations start at the top left.
Come to a free workshop
No coding required. No pitch, because there is nothing to sell.
AI readiness measures whether an organization can put an AI tool to work on its real information. It covers where records live, who may read them, whether anyone counts results, and whether machines can parse your public pages. The score predicts how much groundwork a first AI project needs. It predicts nothing about revenue.
Every finding comes from a public source. The check fetches your home page once, reads your
robots.txt and llms.txt if they exist, and resolves DNS over HTTPS.
It runs no crawl, no port scan, and no intrusive probe.
The ruleset holds 586 vendor fingerprints across 37 categories. They match against the URLs your page tells a browser to fetch, your HTTP response headers, your cookies, and the host allow-list in your Content-Security-Policy. They never match your prose. A page that names a vendor as a customer does not run that vendor, and matching visible text turns every case study into a false positive.
The check reads your robots.txt and reports which of 17 AI crawlers you allow.
Ten of them are search crawlers: OAI-SearchBot, PerplexityBot and
Claude-SearchBot among them, and they decide whether an assistant can cite you.
The other seven are training crawlers like CCBot and
Google-Extended, and they decide whether your text trains the next model.
Blocking the first group costs you citations. Blocking the second costs you nothing. Most
robots.txt files that block AI treat both the same.
Machine legibility carries 18 points, foundations 18, system of record 15, security and privacy 15, measurement 12, prior AI experience 12, and connectedness 10. Connectedness uses diminishing returns, because an organization running fifteen tools is not three times readier than one running five. Scores clamp between 12 and 96: nothing visible from the outside justifies either extreme.
Analysis is passive and best-effort. Sites behind bot protection answer with a 403, and the dashboard says so rather than presenting a thin read as a confident one. Hour estimates and hourly rates are illustrative placeholders meant to start a conversation, not a forecast.
It reads your organization's public website, works out what kind of organization you are, maps the separate systems your data lives in, tests whether AI search crawlers can reach your pages, scores your AI readiness out of 100, and suggests free next steps from Austin AI Hub. It uses public sources only.
Seven weighted components: machine legibility (18 points), foundations such as a shared workspace and modern hosting (18), system of record (15), security and privacy posture (15), measurement (12), prior AI experience (12), and connectedness across systems (10). The dashboard shows what you earned in each. Scores are clamped between 12 and 96 because nothing visible from the outside justifies either extreme.
It depends which crawler. Blocking a search crawler such as OAI-SearchBot, PerplexityBot or Claude-SearchBot means that assistant cannot cite you, even when you are the best answer to someone's question. Blocking a training-only crawler such as CCBot keeps your text out of the next model and costs you no citations. Most robots.txt files that block AI do not make this distinction.
No. It adapts to whatever you are: a nonprofit, a school, a clinic, a city department, a shop, a firm, or a startup. The advice, the privacy obligations, and the example workflows all change to match.
No. Austin AI Hub is a 501(c)(3) nonprofit. Workshops, events, mentorship, and community programs are free. Nothing on this page is a sales pitch, and no one will call you.
No. The Hub's AI literacy sessions are hands-on, led by PhD researchers, and assume no coding at all. They are built for engineers and educators, students and career changers, healthcare workers, small-business owners, parents, and people who have never typed a prompt.
The check fetches your home page once, reads your robots.txt and llms.txt if they exist, and makes public DNS lookups. That is the same information anyone can see. Nothing is stored, nothing is crawled, and no one is contacted.