fkp.my.id — Public API Documentation

Welcome to the public API documentation for this website. This API serves both human developers and automated AI agents (LLMs) with structured JSON data and LLM-friendly Markdown outputs.

[!NOTE] All public API endpoints support standard HTTP Content Negotiation (Accept: text/markdown or Accept: application/json) as well as query string parameter selection (?format=md).

General Information

1. Base URL: https://<domain> (or http://localhost:<port> for local development)
2. Response Formats: application/json (default) and text/markdown (when requested via ?format=md or Accept: text/markdown). Document download endpoint /api/cv returns application/pdf.
3. Default Response Headers:
   • Content-Type: application/json
   • Cache-Control: public, max-age=3600, s-maxage=86400
   • X-Robots-Tag: index, follow

Endpoints

Author Endpoint (/api/author)

Returns author profile information along with supplementary data sections (CV, funding, contact, skills, and socials). Supports both JSON and Markdown formats for developer and AI agent consumption.

• Endpoint: GET /api/author

Query Parameters

Parameter	Type	Description
profile	Flag	Includes primary profile metadata (name, bio, avatar, location, site URL).
cv	Flag	Includes work experience and education history.
funding	Flag	Includes open-source funding platform links.
contact	Flag	Includes public contact channels.
skills	Flag	Includes categorized technical skills.
socials	Flag	Includes social media profile links.
fields	String	Comma-separated list of sections to include (e.g., fields=cv,funding,profile).
format	String	Output format selection: json (default) or md / markdown for formatted Markdown.

Examples

• Retrieve complete author dataset in JSON format

curl -s -X GET https://<domain>/api/author

• Retrieve author profile in Markdown format for AI Agent ingestion

curl -s -X GET "https://<domain>/api/author?format=md"

• Retrieve Markdown format using Content Negotiation header

curl -s -X GET https://<domain>/api/author -H "Accept: text/markdown"

AI Agent and Search Indexing Endpoints

Endpoint Path	Method	Content-Type	Description
/llms.txt	GET	text/markdown	Standardized LLM profile summary file (https://llmstxt.org/).
/.well-known/llms.txt	GET	text/markdown	Well-known standard path alias for AI agent discovery.

Examples

• Retrieve Markdown author profile via llms.txt

curl -s -X GET https://<domain>/llms.txt

Caching, Content Negotiation & Error Handling

Caching Strategy

Public GET requests are cached at edge locations and browser caches using HTTP Cache-Control headers (public, max-age=3600, s-maxage=86400).

Error Responses

All endpoints return standard HTTP status codes (e.g., 400 Bad Request, 401 Unauthorized, 404 Not Found, 500 Internal Server Error) accompanied by a JSON payload describing the error:

{
  "error": "Detailed description of the error encountered."
}

Security & Administration

• Public Endpoints: /api/author, /api/comments, /api/views, /api/search, /api/cv are publicly accessible.
• Admin Endpoints: /api/admin/* routes require active Supabase Auth session tokens (Authorization: Bearer <token>).
• Data Integrity: Input sanitization and parameter validation are enforced across all write operations.

Feedback & Support

For bug reports, feature suggestions, or questions regarding API integration, please submit feedback or contact the administrator via public social channels listed in /api/author?socials=true.