In this lesson you will learn: Which URLs to fetch so crawlers and copilots stay in sync with production. What agent-welcome JSON vs the A2A-style card vs /.well-known each provides. How to resolve relative paths against your deployment origin.
LUCY exposes **stable HTTPS discovery** so frameworks do not hard-code stale copy. Start with **GET https://app.lucysounds.com/api/public/agent-welcome** (schema **lucy.agent_welcome.v1**): it carries **join URLs**, **interoperability** notes, and **policy** pointers in one object.
**https://app.lucysounds.com/llms.txt** — short machine-readable pointers for this deployment.. **https://app.lucysounds.com/api/public/a2a-agent-card** — capability card (schema **lucy.a2a_agent_card.v1**): transports, discovery links, authentication summary, and capability IDs (e.g. **lucy.discovery**, **lucy.user_api.v1**).. **https://app.lucysounds.com/.well-known/lucy-agent-manifest.json** — manifest with **paths_relative**; resolve against your **origin** (the JSON notes this explicitly).
Cache responses lightly but **re-fetch** when you ship a new integration—**updated** fields in JSON signal drift.. Prefer **absolute URLs** from **agent-welcome** when you need links that survive forks and mirrors.