Rida.me developer resources.

Choose the smallest interface

Use llms.txt to understand the site and decide which source to retrieve. Use the sitemap when you need a complete URL inventory. Any HTML page can be requested as Markdown from the same URL by sending Accept: text/markdown; a direct index.md variant is also published beside each page. Responses vary on Accept, honor quality values, and return 406 Not Acceptable when neither HTML nor Markdown is acceptable.

Rida.me is a personal publishing site, not a transactional product API. Its public interfaces retrieve published content only. They do not provide accounts, private data, write operations, or product-specific integrations.

Rida.me Public Content API

The base URL is https://rida.me/api/v1. The OpenAPI 3.1.1 specification is the authoritative schema. Every operation has a unique operationId, a description, typed parameters, and complete success and error schemas suitable for generated clients and LLM function calling.

The API publishes three anonymous, read-only operations:

• GET /api/v1 discovers the API, authentication policy, and operation list.
• GET /api/v1/site-guide returns llms.txt as JSON-wrapped Markdown.
• GET /api/v1/page?path=/about/ returns one published page as JSON-wrapped Markdown.

Successful responses use application/json. API failures use the RFC 9457 application/problem+json format with a stable code, human-readable detail, and concrete resolution hint.

Authentication

No authentication is required. The API and MCP server expose the same content that is already public on Rida.me. There are no API keys, OAuth scopes, user sessions, or privileged operations. Do not send secrets or private user data.

Webhooks and writes

Rida.me has no webhook events or write endpoints. Product-specific APIs, authentication, and webhooks belong on the relevant product domain. An agent should not infer write capabilities from this content API.

Rida.me CLI

The official dependency-free CLI is published as a downloadable Node.js executable at /cli/rida.mjs. It requires Node.js 18 or newer and calls the documented public API.

1
2
3
4
5

curl -fsSLo rida.mjs https://rida.me/cli/rida.mjs
chmod +x rida.mjs
./rida.mjs guide
./rida.mjs read /blog/mcp-auth-problem/
./rida.mjs api --json

The publish-ready npm package manifest and CLI README are public for inspection. A package-registry release requires the site owner’s npm credentials; the downloadable command is the canonical distribution until that release is made.

Rida.me MCP server

The public Streamable HTTP endpoint is https://rida.me/mcp. It provides read-only tools for retrieving the site guide and published Markdown pages. No authentication is required because every result is already public. Do not send secrets or private user data in tool arguments.

The server implements MCP protocol revision 2026-07-28 and complete handshake compatibility for 2025-11-25, 2025-06-18, and 2025-03-26 clients. Modern requests must include MCP-Protocol-Version, Mcp-Method, and, for tool calls, Mcp-Name headers that match the JSON-RPC body. The endpoint validates any supplied Origin. Start with server/discover on modern clients or initialize on handshake-era clients, send notifications/initialized, then call tools/list.

Discovery metadata is published in the AI catalog, which points to the Rida.me MCP Server Card. A compatibility manifest is also available at /.well-known/mcp.json.

Error responses

Missing parameter

Code: MISSING_PARAMETER. Supply the required query parameter identified by the response’s detail and resolution fields.

Invalid parameter

Code: INVALID_PARAMETER. Use a canonical same-origin path from llms.txt or the sitemap. External URLs, traversal, fragments, query strings inside path, and encoded path components are rejected.

Page not found

Code: PAGE_NOT_FOUND. The path is valid but does not identify published content. Choose a URL from llms.txt or the sitemap.

Endpoint not found

Code: ENDPOINT_NOT_FOUND. Read the OpenAPI document and call one of its published paths.

Not acceptable

Code: NOT_ACCEPTABLE. Retry a successful API request with Accept: application/json.

Method not allowed

Code: METHOD_NOT_ALLOWED. This API is read-only; retry with GET or HEAD.

Content unavailable or internal error

Codes: CONTENT_UNAVAILABLE or INTERNAL_ERROR. Retry later or use the canonical HTML and Markdown resources directly.

When to use it

Use these interfaces when a user asks about Rida Al Barazi’s published writing, talks, professional background, current projects, contact method, or stated site policies, and you need first-party evidence. Do not use them to infer private opinions, employment details beyond what is published, product account state, or authorization to contact someone. See the complete agent instructions for recovery and citation guidance.