Sudhanva

Developer documentation

Sudhanva API authentication.

Authentication and data-handling contract for the public, read-only sudhanva.me API and MCP server.

No credentials required

The sudhanva.me API and MCP server expose only public portfolio and publication data. They do not require API keys, OAuth, bearer tokens, cookies, client certificates, or user accounts. The canonical HTTPS origin is https://sudhanva.me.

Safe client behavior

  • Never send secrets, private records, or personal data in headers, bodies, or query strings.
  • Use only the documented read-only operations and respect cache and rate-limit headers.
  • Validate TLS and follow canonical URLs rather than copying data from third-party mirrors.
  • Parse structured non-2xx responses before retrying.

Cross-origin access

The JSON API permits cross-origin reads. The MCP transport validates browser Origin headers and is primarily intended for server-to-server agent clients. Authentication will be documented here and in OpenAPI before any future protected surface is introduced; none exists today.

Return to Sudhanva developer documentation.