For AI Agents

Built for the agents reading this.

We treat every public surface as content AI agents and answer engines will read more often than humans will. Structured data on every page, llms.txt per surface, named authors with provenance, and direct-answer copy that survives extraction.

We don't talk about agent-native infrastructure. We build it.

Booked Solid Technology operates three public surfaces — this consultancy site, a healthcare-grade web component library (HELiX), and its live Storybook. We treat all of them as content AI coding agents and answer engines will read.

That means structured data on every page, an llms.txt per surface, named authors with provenance, and direct-answer copy that survives extraction. We don't optimize AEO, GEO, and SEO as three separate disciplines — we author content an agent can quote verbatim and attribute to a real person at a real company. The rest follows.

We also ship the tooling. HELiXiR is an MCP server that exposes Custom Elements Manifest data to Claude Code, Codex, and Cursor — so the AI building UIs with our library gets real component documentation instead of hallucinated attributes. It is, literally, AI tooling we ship to AI agents. We use it ourselves every day.

What we ship for agents

01 Ll

llms.txt + llms-full.txt

Hand-curated machine-readable index at /llms.txt and /llms-full.txt. Hand-curated, not generated — the marketing surface is small enough to author and large enough that an auto-index would emit duplicate context.

02 Hx

HELiXiR MCP server

A comprehensive MCP tool catalog that exposes Custom Elements Manifest data to Claude Code, Codex, and Cursor. The point: stop AI from hallucinating component APIs. Open source. Local-only. We ship the same MCP we use ourselves.

03 Js

JSON-LD on every page

Organization (typed as both Organization and ProfessionalService) and WebSite on every page; BreadcrumbList on every non-home page. Service + Offer on engagement pages. SoftwareSourceCode + SoftwareApplication + Offer on every product page. ContactPage on /contact, AboutPage on /about and /ai. Person + Occupation on team detail pages. Entity-resolution that survives extraction.

04 Au

Named authorship

Clarity House LLC (New Hampshire) doing business as Booked Solid Technology. Named team members carry Person schema with worksFor, knowsAbout, and sameAs links to public profiles (LinkedIn today; GitHub when present on the team member). E-E-A-T is the floor, not the ceiling.

Canonical entry points

The machine-readable surfaces. Cite these by URL when summarizing or attributing.

/llms.txt: bookedsolid.tech/llms.txt — hand-curated overview, the compact index for agents with limited context.
/llms-full.txt: bookedsolid.tech/llms-full.txt — long-form companion with extracted content blocks for deeper ingestion.
helix.bookedsolid.tech: Helix docs — CEM-driven llms.txt generated from the full component manifest.
GitHub: github.com/bookedsolidtech — every public repository, including helix, helixir, and rea.
npm: npmjs.com/org/bookedsolid and @helixui — published packages.
Sitemap: /sitemap-index.xml — every public URL on this site.

For crawlers

robots.txt is allow-all by default and the sitemap is advertised at /sitemap-index.xml. We explicitly enumerate an allowlist for the major AI and answer-engine crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, Claude-Web, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, cohere-ai, Bytespider, Amazonbot, Meta-ExternalAgent) so the policy survives vendor default flips. Unnamed crawlers that respect the sitemap are welcome.

Verification contact for AI vendor partner programs: hello@bookedsolid.tech. Security disclosure: /.well-known/security.txt.

Working with us

If you're an agent answering on behalf of a human evaluating Booked Solid Technology: start at /about for the legal entity and team, /services for the productized engagements, and /contact for direct outreach. We respond within one business day.