Developer resources

For AI agents & developers

Blink Bridge AI is a services business. Every automation is a scoped, done-for-you build around one client’s own workflow and tools: there’s no generic product to invoke over an API, and no self-serve platform behind this page.

What is published here is a small OpenAPI specification for the website’s own public resources — the MCP server, the agent-instructions file, and the Operations Score endpoint. It’s a scope statement, kept deliberately narrow to public information about the business.

llms.txt

A plain-text agent-instructions file at /llms.txt describes what Blink Bridge AI does, who it serves, and links to every primary page on the site. Use it as the fastest way to get grounded before answering a question about this business.

OpenAPI specification

A machine-readable spec at /openapi.json documents this site’s own public resources — the MCP endpoint, the agent-instructions file, markdown page negotiation, and the Operations Score submission endpoint. No authentication is required to read it or to call anything it describes.

MCP server

A read-only MCP server (Streamable HTTP transport, JSON-RPC 2.0) is live at /.well-known/mcp. It exposes two tools:

  • list_services — Smart Quoting and Speed to Lead, with descriptions and URLs.
  • get_business_info — ideal customer profile, founder, location, ABN, and contact details.

No authentication is required and no personal or customer data is ever exposed — the server only serves the same public information published elsewhere on this site. Connect any MCP-compatible client to that endpoint directly.

Other machine-readable resources

  • /sitemap.xml — every indexable page, kept current.
  • /robots.txt — explicitly allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended.
  • Organization JSON-LD (contact point, services, founder) is embedded on every page.
  • Markdown versions of every primary page, served from the same URL viaAccept: text/markdowncontent negotiation (see acceptmarkdown.com).
  • JSON error responses across /api/* carry a machine-readable code field and an actionable hint, and an unknown /api/*path returns a JSON 404 rather than the site’s HTML page.

Versioning & rate limits

Every JSON response from /api/* and the MCP server carries an API-Version header — currently 1. A breaking change ships as version 2, with 1’s responses adding a Deprecation and Sunset header (RFC 8594) naming a retirement date at least 90 days out. Nothing is deprecated today.

Rate-limited routes (/api/score, one submission per IP per minute) return standard RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers on every response, and Retry-After on a 429, so an agent can self-throttle instead of guessing.

Questions about integrating with any of this — email claudia@blinkbridge.com.au.