Korea4Home agent and public resource documentation

When to use this site

Start with the public resource index and usage instructions. Choose a relevant hub, follow its canonical page links, and cite the original public page. Check the publication date and the terms on each listing.

Read-only resources

• GET /llms.txt returns Markdown instructions and a curated index.
• GET /llms/hubs/{section}.md returns a public hub and a bounded list of recent public records. Use the section links in the index. An unavailable section returns 404.
• GET /openapi.json returns the OpenAPI contract for the JSON resource API. Markdown formats are documented here.
• GET /api/public/resources returns the public index as JSON. Add ?section=home or another available section to read a hub.
• GET /sitemap.xml identifies indexable public URLs. Hub samples are not a complete inventory.

These public, anonymous resources require no authentication. They expose public content only and do not support writes. Private account and administrative APIs are outside this contract.

curl -H 'Accept: text/markdown' https://korea4home.com/
curl https://korea4home.com/llms.txt
curl https://korea4home.com/llms/hubs/home.md
curl https://korea4home.com/openapi.json

MCP connection

Connect a Streamable HTTP client to https://korea4home.com/mcp. Discover it through the MCP manifest. The server supports initialization, ping, tools/list, and tools/call. It is stateless and returns JSON responses. GET returns 405 because there is no server event stream.

The two tools are get_public_resource_index with an empty argument object and get_public_resource_hub with a section string from the index. Results contain sourceUrl, mimeType, and text. Both tools read the same public documents as the website and API. They cannot query arbitrary database fields, change listings, read private accounts, send messages, or make payments.

curl https://korea4home.com/api/public/resources?section=home
curl -X POST https://korea4home.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -H 'MCP-Protocol-Version: 2025-11-25' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

MCP accepts protocol versions 2025-11-25, 2025-06-18, and 2025-03-26. Requests have a 16 KiB body limit. Unsupported versions, malformed requests, invalid tool arguments, and unknown methods return protocol errors. Unknown hubs and temporary data failures return tool errors. Browser requests must use the canonical site Origin; native clients may omit Origin. Public tools require no authentication.

Response formats and errors

Send Accept: text/markdown to the homepage for its public Markdown resource guide. Send Accept: text/html for the website. Negotiated responses include Vary: Accept. Missing unmatched addresses return HTTP 404 with a Markdown recovery guide when Markdown is requested.

The Markdown index and hubs use text/markdown; charset=utf-8. Unknown sections return HTTP 404. Unsupported methods return HTTP 405. A temporary server failure can return 5xx; retry later with backoff. The JSON API accepts 600 requests per 60 seconds per server process. This service quota is shared across callers. Responses include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset (seconds), and RateLimit-Policy. A 429 response includes Retry-After. These quota headers describe the JSON API, not the Markdown documents or MCP tools. Pagination, write idempotency, webhooks, and payments do not apply to these read-only documents.

API versioning and deprecation

Send Korea4Home-API-Version: 1 to select the JSON API contract. Omitting the header also selects version 1. An unsupported version returns a structured HTTP 400 error. Responses identify the version in the same header. Breaking changes require a new version. Version 1 will remain available for at least 90 days after a deprecation announcement in these docs. Deprecation and Sunset response headers will identify a scheduled retirement. No retirement is currently scheduled.

User actions and access policy

Listing submissions, account changes, messages, and payments use the signed-in website and its permission checks. These documents do not authorize an agent to act for a user. Follow robots.txt, Privacy, and Terms.