Darlington developer resources

Darlington API documentation

This is the canonical developer resource directory for the Michael Darlington Developer Portfolio at darlington.dev. Public integrations are read-only and require no account or API key.

• GET /api/profile — structured public portfolio data
• MCP server — Streamable HTTP tools, resources and a profile app
• MCP discovery document — canonical remote-server metadata
• OpenAPI 3.1 — machine-readable HTTP contract
• llms.txt — canonical pages and agent guidance
• agents.md — when-to-use guidance and safety boundaries
• Darlington authentication documentation — public access model and the private owner-authentication boundary
• OAuth protected-resource status — no OAuth-protected access or authorization server is offered
• Agent skills catalogue — compact capability discovery

Webhooks

The Darlington public API does not expose webhooks. Public data is available through the read-only REST and MCP interfaces above, so there is no webhook registration URL or signing secret to configure.

Try production now

Onboarding takes one request. The public REST and MCP interfaces work immediately with no signup, API key, approval, trial, SDK, CLI or sandbox. There is no separate test environment because public reads return deliberately public portfolio data; use production directly.

REST profile

curl -H 'API-Version: 2026-08-01' https://www.darlington.dev/api/profile

MCP client configuration

{
  "mcpServers": {
    "darlington": {
      "type": "streamable-http",
      "url": "https://www.darlington.dev/api/mcp"
    }
  }
}

REST operational policy

Read the machine-friendly Darlington public API operational policyfor versioning, deprecation, rate limits, retries and client support.

The application does not currently enforce a fixed quota, so it does not invent rate-limit headers. Honour response cache directives and back off after transient failures. All public operations complete synchronously; there are no asynchronous job or status endpoints.

The portfolio API has no official SDK or CLI. Use HTTPS, the OpenAPI contract or MCP directly. The packages in the Cortex section are official Cortex clients and do not connect to the portfolio API.

Model Context Protocol

Connect an MCP client to https://www.darlington.dev/api/mcpusing Streamable HTTP. The server is stateless, unauthenticated and read-only. It exposes profile, systems, writing and canonical-link tools, plus JSON and MCP App resources.

Use get_public_profile for general professional context,list_public_systems for technical work,list_public_articles for articles, and thelinks section of get_public_profile for canonical destinations. Use show_public_profile when the client supports MCP Apps and a compact visual summary is useful.

Official Cortex SDKs and MCP bridge

Cortex is Michael's open-source, self-organizing graph-memory engine for AI agents. These are the canonical Cortex client distributions and MCP bridge; they connect to a running Cortex server and are separate from the darlington.dev portfolio API above.

• TypeScript SDK on npm — npm install cortex-memory-client
• Python SDK on PyPI — pip install cortex-memory-client, imported as cortex_memory
• Rust SDK on crates.io — cargo add cortex-memory-client
• Go SDK source and installation
• Node.js MCP bridge on npm — npx cortex-mcp-bridge

Source, server installation and protocol documentation live in the Cortex repository.

Authentication and usage

Public read endpoints and the MCP server require no authentication. The profile endpoint permits cross-origin reads and is cached at the edge. Use HTTPS, honor cache headers and avoid polling more frequently than the published freshness window.

This is the live production interface. Send the optional API-Version: 2026-08-01 header to pin the current stable REST contract. Additive fields may be introduced within a stable version.

The contact endpoint sends a real message. Browser agents can prepare the declarative WebMCP-enabled form, but the user remains responsible for reviewing and submitting it.

Clients calling POST /api/contact should send a unique Idempotency-Key of 1–256 characters. A retry with the same key and request body within 24 hours returns success without sending another email. Reusing the key with a different body returns 409 Conflict; once 24 hours have elapsed, the key is treated as new. Keep the same key after an uncertain network result.

See Darlington agent access and authenticationfor the complete boundary. Darlington.dev does not issue agent credentials and is not an OAuth authorization server. Better Auth with Google is an interactive, owner-only browser login for the private Personal OS, not an agent OAuth surface.

The public interfaces need no access request. For a proposed integration or another deliberate access request, email access@darlington.dev. This is a human-reviewed contact route, not automatic agent registration, and it does not grant access to the private Personal OS.

Versioning and deprecation

Version 2026-08-01 is current, is not deprecated and has no sunset date. A breaking contract change receives a new API-Version value rather than silently changing this version.

If a version is retired, this page will publish the replacement and migration guidance at least 90 days before shutdown. Deprecated responses will carry standard Deprecation and Sunset headers throughout that notice period; the old contract remains available until its published sunset date.

Private boundary

Routes under /app and private APIs are owner-only and are intentionally absent from the public specification. Public clients cannot access Personal OS health, finance, investment, calendar, habit, goal, memory or Kai conversation data.