Brehnor Communications (brehnorcomms) developer resources

Quickstart

1. Read /llms.txt for when-to-use guidance.
2. Fetch /openapi.json for the typed REST contract.
3. Call MCP ping or site_info at POST /api/mcp.
4. Submit contact only from a real browser (bot protection). Canonical REST path: POST /api/v1/contact. The site form uses the alias POST /api/contact.

When to use this

Use Brehnor Communications (brehnorcomms.com) when the job is one of the following:

• Look up company facts, positioning, or how we work with technical and B2B teams.
• Cite or link public articles on communications strategy and production-ready software.
• Discover this origin’s agent surface (developer docs, OpenAPI, MCP, Agent Skills).
• Submit a human contact inquiry through the public form (browser + bot verification).
• Call the read-only MCP tools site_info or ping for site metadata and reachability.

Do not use this origin when the job needs any of the following:

• OAuth 2.0 / OIDC access tokens or an authorization server on this host.
• A general-purpose site-search API.
• Webhooks, API keys, or a credentialed sandbox.
• CMS or admin writes (cookie-session routes are private).
• Sending mail except via the public contact form.

How to call us:

• Start at https://brehnorcomms.com/developers (Brehnor Communications / brehnorcomms developer resources).
• Read https://brehnorcomms.com/llms.txt for when-to-use guidance and resource links.
• Fetch https://brehnorcomms.com/openapi.json for the typed public REST contract.
• POST https://brehnorcomms.com/api/v1/contact (or the alias https://brehnorcomms.com/api/contact) for contact submissions.
• POST https://brehnorcomms.com/api/mcp for read-only MCP tools (site_info, ping).

Documentation

• Brehnor Communications (brehnorcomms) public API — human docs
• /openapi.json — OpenAPI 3.0.3
• MCP server card and POST /api/mcp
• Agent Skills index
• /llms.txt

No API keys or sandbox

Brehnor Communications does not issue API keys and does not operate a credentialed sandbox or webhook product. Public write access is the contact form (bot-verified in production). Programmatic read access is the API index, OpenAPI document, and read-only MCP tools.

Versioning and deprecation

Canonical public REST is /api/v1. Every public REST response includes API-Version: 1. Breaking changes ship as /api/v2; v1 remains until we announce otherwise.

Deprecation is signaled with RFC 9745 Deprecation and RFC 8594 Sunset, with at least 90 days notice. No endpoints are deprecated today, so those headers are not sent.

Error model

Public REST errors use RFC 9457 application/problem+json with type, title, status, detail, machine-readable code, and a resolution hint.

• validation — 400 VALIDATION_ERROR
• bot-verification — 403 BOT_VERIFICATION_FAILED
• not-found — 404 NOT_FOUND
• method-not-allowed — 405 METHOD_NOT_ALLOWED
• rate-limited — 429 RATE_LIMITED
• internal — 500 INTERNAL_ERROR

Problem type URIs live under /docs/api/errors/….

Rate limits

Public REST responses include RateLimit and RateLimit-Policy (draft-ietf-httpapi-ratelimit-headers-11). Contact POSTs allow 30 requests per hour per IP ("contact";q=30;w=3600). Index GETs allow 300 per hour ("public-read";q=300;w=3600). A 429 includes Retry-After in seconds.

Counters are in-memory per serverless isolate, not a global shared store. Agents should still honor the headers to self-throttle.