# Swap Meet Connect — Agent Authentication > Status: public read-only access today. No third-party OAuth server yet. ## What agents can do without authentication The following surfaces are fully public. Crawl, read, and cite them freely (subject to the Content-Signal directives in `/robots.txt`): - Marketplace listings — - Builders Library guides and calculators — - Swap meet events — - Daily news — - Public project showcases — The raw data is also available via the public REST endpoints advertised in [`/.well-known/api-catalog`](/.well-known/api-catalog). ## Write actions (create listing, message a seller, manage inventory) Write actions require an authenticated human user. There is currently **no programmatic OAuth flow for third-party agents**. To enable an agent to act on a user's behalf: 1. The human user creates an account at . 2. The user signs in and uses the in-app UI directly. If you are building an agent product that needs delegated write access, contact the Swap Meet Connect team at with a description of the use case so we can prioritize an OAuth/MCP server. ## Planned: MCP server An MCP (Model Context Protocol) server is planned. The stub server card lives at [`/.well-known/mcp/server-card.json`](/.well-known/mcp/server-card.json) with `status: "planned"`. When the server is live, the `transport` field will be populated and `status` will change to `"active"`. ## Content Signals See [`/robots.txt`](/robots.txt) for our `Content-Signal` directives: ``` Content-Signal: ai-train=no, search=yes, ai-input=yes ``` - `ai-train=no` — please do not use our content to train models. - `search=yes` — index us for traditional and AI search. - `ai-input=yes` — you may use our content as grounding/RAG input when answering user questions, with attribution and a link back.