RAG: the pages it generated
Retrieval-augmented generation over this dealer's data. Every vehicle and store page is expanded into plain-text Markdown you can browse below, pull as one bulk corpus, or query live with the rag_search tool.
How the RAG corpus works
Each vehicle and store page is written out as clean Markdown and concatenated into a single bulk corpus, llms-full.txt (2,630 KB). An agent can ingest the whole corpus, or call rag_search(query) over the MCP endpoint to retrieve just the matching chunks with source links. Everything below is a real generated page you can open.
Every document is checked against an admission policy before it joins the corpus. Search-results and filter pages are refused, interface furniture and text that repeats across the corpus is removed, thin and near-identical documents are refused, and each refusal is recorded with its reason.
| Document type | Documents |
|---|---|
| site | 131 |
| Measure | Value |
|---|---|
| Documents evaluated for admission | 133 |
| Admitted | 131 |
| Refused | 2 |
| Average unique words per admitted document | 659.1 |
| Repeated blocks lifted into a single document | 25 |
| Near-duplicate ratio | 0.0 |
| Reason | Documents |
|---|---|
| Too little unique content | 2 |
All 575 vehicles are in the corpus as one Markdown record per VIN, addressed by the pattern https://ai.castlehyundaioaklawn.com/v/{VIN}.md (and https://ai.castlehyundaioaklawn.com/v/{VIN}.json). A few samples:
rag_search(query, limit?) over the MCP endpointhttps://ai.castlehyundaioaklawn.com/v/{VIN}.mdcurl -s -X POST https://ai.castlehyundaioaklawn.com/api/ucp/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"rag_search","arguments":{}}}'