マシンリーダブルなインターフェース

ZensInk Developers

Everything an agent or integrator needs to work with zens.ink programmatically. Machine-readable first: specs over prose, JSON over HTML, markdown on request.

API

The OpenAPI 3.1 specification is published at /openapi.json. Every operation has a unique operationId, typed schemas, and documented error responses — suitable for direct LLM function-calling.

Endpoint	Method	operationId	Purpose
/api/checkout	POST	createCheckout	Create a hosted checkout session
/api/purchase-status?rid=	GET	getPurchaseStatus	Poll payment status; returns license key on completion
/api/verify-key	POST	verifyLicenseKey	Validate a license key, mint a 10-minute download token
/api/download?t=	GET	downloadProPackage	Download the watermarked Pro ZIP
/api/webhook	POST	creemWebhook	Payment webhook (HMAC-signed, internal)

All API errors are structured JSON, never HTML:

{
  "error": "Missing request ID.",
  "status": 400,
  "hint": "See https://zens.ink/openapi.json ..."
}

CLI

The free CLI tools are pure Python stdlib — zero pip dependencies, clone and run, MIT licensed.

pip install git+https://github.com/ZensInk/zens-ink-seo-package.git

# discover long-tail keywords (no API key needed)
python3 -m zens_ink.keyword_research --seed "astro" --lang en

# full list: https://github.com/ZensInk/zens-ink-seo-package

MCP server

The package ships an MCP stdio server exposing every CLI tool as a callable tool — point any MCP client at it:

python3 -m zens_ink.mcp

Markdown content negotiation

Every content page on zens.ink (home, journal posts, docs, this page) is available as raw markdown. Send Accept: text/markdown on any page URL:

curl -H "Accept: text/markdown" https://zens.ink/journal/seo-for-developers/

Responses carry Vary: Accept so caches keep the HTML and markdown variants separate.

Machine-readable files

• /openapi.json — OpenAPI 3.1 API specification
• /llms.txt — curated agent index
• /llms-full.txt — full site map for agents
• /sitemap.xml — XML sitemap
• /rss.xml — Journal RSS feed

When to use ZensInk

• Keyword research without paid APIs — autocomplete discovery, volume lookup, SERP difficulty
• Technical SEO audits of static builds (broken links, meta, GEO readiness)
• Competitor content-gap analysis from sitemaps
• Pro workflow automation: clustering, KGR scoring, priority matrices, full audits