dare-co-uk — agent-discoverability generated

DARE-CO-UK · AGENT-DISCOVERY · 10 MAY 2026

Re-generated agent-discoverability artefacts from agent-config.json. The config is the brand voice; the script is the templating substrate.

TL;DR

3 artefact(s) written to /Users/dansellars/Code/dare-co-uk
llms.txt (2,379 bytes)
.well-known/ai-agents.json (3,071 bytes)
_includes/agent-jsonld.html (940 bytes)

What this enables

/llms.txt — primary agent-discoverability file. LLMs and AI-agent crawlers reach for this first. Sectioned markdown so it ingests cleanly and a human can skim it.
/.well-known/ai-agents.json — structured equivalent for machine parsers; the well-known prefix is the IETF convention for site-level metadata files.
<script type="application/ld+json"> snippet — schema.org Organization markup, drop into the homepage <head>. Search engines use this; LLMs increasingly cite it when answering “who runs X?” questions.

Next steps

Review agent-config.json in the repo — the defaults Dan should rewrite to brand voice. Especially the summary, why_us, why_now, and key_pages sections.
Embed the JSON-LD snippet in the homepage <head> (_includes/agent-jsonld.html). Once embedded, every homepage render carries it.
Commit + deploy — llms.txt and .well-known/ai-agents.json go live as static files on the same domain.
Verify with crawlers — once live, hit https://<site>/llms.txt and https://<site>/.well-known/ai-agents.json to confirm both respond 200 with the expected content.

Portfolio note

Same script, same config schema, different brand voice. Drop agent-config.json into the dogwood / audrey / client repo, run dare_agent_discoverability.py --repo ~/Code/<that-repo>, ship.

Generated 2026-05-10 12:08:05 via dare_agent_discoverability.py. Source: /Users/dansellars/Code/dare-co-uk/agent-config.json.

Source: dare_agent_discoverability_2026-05-10.md · Rendered 2026-05-10 12:08