# Bailey Engineering — agent services status

Last updated: 2026-05-05

## Overview

Bailey Engineering operates [baileyengineers.com](https://baileyengineers.com/) as a static public marketing site for civil-engineering and land-planning services in southern Idaho. There is no public API, no OAuth/OIDC authorization server, no protected endpoints, and no MCP transport at this origin. This document describes Bailey's current posture toward AI/agent service-discovery standards and explains why certain spec-mandated discovery files are published as **disclosure stubs** rather than fabricated metadata.

## Currently available

- **Content-Signal directives** in [/robots.txt](/robots.txt) — `Content-Signal: ai-train=yes, search=yes, ai-input=yes`, aligned with Bailey's AI-visibility strategy
- **Agent-skills discovery index** at [/.well-known/agent-skills/index.json](/.well-known/agent-skills/index.json) with four skill documents (site navigation, contact, service-area research, client-page access)
- **Markdown twins** for major landing pages — `/index.md`, `/about.md`, `/services.md`, `/service-areas.md`, `/contact.md`. Advertised in HTML head via `<link rel="alternate" type="text/markdown">`
- **Link header on every response** — `Link: </.well-known/agent-skills/index.json>; rel="service-desc"; type="application/json"` (RFC 8288 / RFC 8631)
- **Sitemap** at [/sitemap-index.xml](/sitemap-index.xml)

## Disclosure stubs published

The following spec-mandated discovery paths are published as **minimal-valid metadata documents with empty `*_supported` arrays**. They exist so that:

1. **Audit tooling** that checks for presence-of-file gets a 200 response and clear metadata rather than a 404 ambiguity.
2. **Spec-compliant clients** see "no flows available / no servers / no capabilities" in the metadata and stop trying.
3. **The disclosure is unambiguous** — each stub's `$comment` (or `description`) field states explicitly that Bailey does not operate the service.

| Path | Spec | Status |
|---|---|---|
| [/.well-known/oauth-authorization-server](/.well-known/oauth-authorization-server) | RFC 8414 | Empty stub — no OAuth 2.0 authorization server operated |
| [/.well-known/openid-configuration](/.well-known/openid-configuration) | OpenID Connect Discovery 1.0 §3 | Empty stub — no OpenID Connect provider operated |
| [/.well-known/oauth-protected-resource](/.well-known/oauth-protected-resource) | RFC 9728 | Empty stub — no protected resources; site is fully public |
| [/.well-known/mcp/server-card.json](/.well-known/mcp/server-card.json) | SEP-1649 / PR-2127 (in-flight) | Empty stub — no MCP server hosted |

These stubs are **not** placeholders for future development. They are honest disclosures that the corresponding services do not exist at this origin.

## No stub published

- **WebMCP browser-side tools.** Bailey's site has a zero-client-JavaScript posture. Implementing `navigator.modelContext.provideContext()` would require client-side JS for tools that are already trivially accessible via the static surface: search via [/search/](/search/), service areas via the agent-skills index, contact via URL parameters on [/contact/](/contact/). No file is published because WebMCP is a JS API, not a `.well-known` document.

## When this changes

If Bailey ever publishes a real public API, OAuth flow, OIDC provider, or MCP endpoint, the corresponding disclosure stub will be replaced with real metadata. Until then, the stubs are explicit "not applicable" markers.

## Contact

For questions about Bailey's services or APIs:

- Phone: (208) 938-0013
- Email: projects@baileyengineers.com
- Contact form: [/contact/](/contact/)