API Documentation

Updated: August 20, 2026

Intelligink publishes two read-only APIs so that AI agents, MCP clients, and other automated consumers can work with what we publish without scraping the site. Both are public, require no authentication, and expose nothing beyond the content already on intelligink.com.

The two APIs are listed in our API catalog, served at /.well-known/api-catalog per RFC 9727 in the RFC 9264 linkset format. An agent that knows the domain can find everything below from that one document.

Content Index API

A single JSON document containing the full text of every published article and of our public service and company pages.

  • Endpoint: GET https://intelligink.com/index.json
  • Description: OpenAPI 3.1
  • Media type: application/json

There are no query parameters — fetch the whole document and filter client-side. Every entry carries a hash of its text, so a consumer that stores those hashes can tell a real content change from a rebuild without diffing bodies. The document is regenerated on each site build, and generated records when that was.

Pages are included only when they have been explicitly approved for the feed; everything else on the site stays out of it by default.

MCP Server

A Model Context Protocol server that gives an AI agent structured access to the same content, including semantic search.

Point any MCP client at https://mcp.intelligink.com/mcp. The server is stateless and issues no session identifier. It advertises five tools:

Tool What it returns
get_company_profile Who Intelligink is and where we focus.
get_services The Intelligink service catalog.
search_content Semantic search across everything we publish.
list_recent_articles The latest articles, newest first.
get_article The full text of one article, by slug.

The OpenAPI document above describes the HTTP transport so the endpoint can be discovered and reached. The JSON-RPC method set is the Model Context Protocol’s own, and the server reports it in response to initialize and tools/list.

The MCP Server Card is the same information in the shape MCP clients look for — identity, transport, and supported protocol versions, per SEP-1649. It deliberately does not list the tools above: a server’s surface is dynamic, so clients are expected to call tools/list at connect time rather than trust a static document.

Authentication

There isn’t any. Every endpoint above is public, read-only, and unauthenticated — no registration, no credentials, no token exchange. /auth.md states that in the form an AI agent expects to read it, and explains why no OAuth metadata is published.

Terms of use

Both APIs are provided as-is for reading and referencing our published content, under our terms and conditions. If you are building something on top of them and need a guarantee we do not currently offer — a stable schema, a rate limit, an SLA — please reach out and let’s talk.