Agent access

Public API documentation.

The API provides access to content already published on this site. It does not accept confidential information or replace an advisory conversation.

Authentication and scope.

No API key, account, or token is required. Public reads use GET and HEAD; OPTIONS reports available methods. There are no write, booking, assessment, client-record, or form-submission operations.

OpenAPI 3.1 · llms.txt · Sitemap

Two read operations.

  • GET /api/v1/pages/: listPublicPages. Paginated directory. Optional language is en or es. limit is an integer from 1 to 100 (default 20). offset is an integer from 0 to 100000 (default 0). Returns items, total, limit, and offset.
  • GET /api/v1/page/?path=/advisory-model/: getPublicPage. path is required and must be a site-relative page path, not an external URL. Returns path, url, title, description, language, and markdown. Cite the canonical url in the response.

Unique operation IDs, typed parameters, and response schemas support OpenAPI-compatible tool import. This is not an MCP server or a tool that makes decisions on a client's behalf.

Example requests.

curl -sS -L -H 'Accept: application/json' 'https://www.ankerbioss.com/api/v1/pages/?language=en&limit=20&offset=0'
curl -sS -L -G -H 'Accept: application/json' --data-urlencode 'path=/advisory-model/' 'https://www.ankerbioss.com/api/v1/page/'

Markdown at the same URL.

Pages, including the homepage, serve Markdown for Accept: text/markdown and HTML for Accept: text/html. Responses include Vary: Accept. Quality weights are honored; ties prefer HTML. Unsupported representations return 406. Static files, including images, robots.txt, and OpenAPI, retain their own formats.

Markdown is generated from the main HTML content at each deployment, retaining links and citations while excluding navigation, forms, and scripts. Dynamic responses use Cache-Control: private, no-store to avoid mixing representations.

curl -sS -L -i -H 'Accept: text/markdown' 'https://ankerbioss.com/'
curl -sS -L -i -H 'Accept: text/html' 'https://ankerbioss.com/'

Errors with a recovery action.

A missing page retains status 404 and returns a Markdown explanation when that format is requested. API errors use application/problem+json following RFC 9457: type, title, status, detail, and instance, plus code, hint, and docs. Invalid parameters return 400; unknown pages or operations, 404; write methods, 405; unacceptable formats, 406.

curl -sS -L -i -H 'Accept: text/markdown' 'https://ankerbioss.com/page-that-does-not-exist/'

Do not retry a 400 without correcting the request. For a 404, consult the directory. Unexpected application failures return a safe 500 response. Errors generated by hosting infrastructure may differ.

Responsible use and limits.

Use modest concurrency and pagination; no fixed request-rate quota or availability SLA is promised. Honor Retry-After if hosting infrastructure returns it. Content reflects the latest deployment, not real-time client information. Do not send personal or confidential information in query parameters.

Use these pages to identify services, consult published terms, and cite the firm's approach. Do not use them to rate candidates or make appointment decisions. For a specific engagement, start a conversation with Anker Bioss.