Developer and Agent Portal

When to use this portal

When researching Digital Engine articles about SEO, digital marketing, content strategy, web analytics, AI, or automation, start here or with llms.txt. These interfaces are for agents that need to search public content, retrieve article metadata, read Markdown, or use WebMCP in a supported browser. Everything is public and read-only, with no login, API key, account, or browser JavaScript required.

Quick start

• Content index: Metadata, canonical URLs, and Markdown URLs for articles and saved Facebook notes.
• OpenAPI 3.1:All public JSON endpoints, parameters, response schemas, and typed errors.
• API Catalog:An RFC 9727 catalog of the OpenAPI document, content collections, and MCP endpoint.
• MCP Server Card: A description of the stateless, streamable HTTP MCP server, which requires no authentication.
• Agent Skill: A workflow for finding, evaluating, and citing content from this site.
• Auth.md: Why this site requires no registration, token, or credential.

REST API and versioning

The current stable version is version 1. API clients may omit the header to use the current version, or send X-API-Version: 1 to select version 1 explicitly. Successful and error responses both return X-API-Version: 1.

If a future change is incompatible, a new version will be released while the existing version remains available for a reasonable migration period. Any endpoint scheduled for removal will be announced with Deprecation and Sunset response headers, on this page, and in the OpenAPI description. No endpoint is currently deprecated.

GET /api/content.json
Accept: application/json
X-API-Version: 1

Error handling

API errors use HTTP status codes and JSON bodies, never an HTML app shell. The error body includes a machine-readable code, a human-readable message, and a hint that can help the client recover.

{
  "error": {
    "code": "not_found",
    "message": "The requested public content item was not found.",
    "hint": "Use /api/content.json to discover valid content."
  }
}

MCP and WebMCP

The MCP endpoint is at /mcp and supports initialize, ping, tools/list, and tools/call. It exposes only two read-only tools, search_content and read_content. It cannot log in, buy, write, delete, or act on a user's behalf.

Browsers with WebMCP support can use the read-only digital_engine_search_content and digital_engine_read_content tools directly from the page. Their site-specific names distinguish them from the MCP HTTP endpoint tools, search_content and read_content. Other clients can still use Markdown, the JSON API, or the MCP HTTP endpoint.

Scope and limitations

Digital Engine is a public content archive, not a SaaS product or transaction platform. It does not issue API keys and has no sandbox, account management, payments, orders, comments, or write API. Historical interfaces, policies, product features, and external links in the articles may have changed. For questions about current conditions, check the latest primary sources from the relevant service.

To discuss SEO, AI, content strategy, automation, or the site experience, visit the contact page.