Vikranth Reddimasu Developer Portal
Public, read-only access to portfolio data for agents, recruiters, and developer tools. The API and MCP server expose the same public information shown on this website.
Quickstart
No account or API key is required. Fetch the versioned JSON profile directly:
curl --fail-with-body https://vikranthreddimasu.me/api/v1/profileStart at the API index, inspect the OpenAPI 3.1 specification, or use llms.txt when markdown is a better fit.
Sandbox
The production profile endpoint is the sandbox because every operation is public, read-only, idempotent, and has no side effects. Open the live JSON response and test requests without credentials or test data. A separate environment becomes useful only if write or authenticated operations are added later.
Errors
REST errors use RFC 9457 application/problem+json. Every error includes type, title, status, detail, instance, a stable code, and a resolution hint. Unknown paths under /api/ use this model instead of returning HTML.
Rate limits
Public API responses advertise 60 requests per 60 seconds through RateLimit-Policy and RateLimit, plus the widely supported RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset compatibility fields. A 429 response also includes Retry-After. Clients should slow down before the remaining quota reaches zero.
Versioning and deprecation
Breaking REST changes receive a new URL major version such as /api/v2. Compatible optional fields and endpoints may be added within v1. When an operation is deprecated, its documentation and response include Deprecation and a Link to migration guidance. Once a retirement date is chosen, a Sunset header gives at least 180 days of notice. The existing /api/profile path remains a compatibility alias; the canonical operation is /api/v1/profile. Read the complete versioning and deprecation policy.
MCP
Connect a Model Context Protocol client to https://vikranthreddimasu.me/mcp using Streamable HTTP. The read-only get_vikranth_profile tool has typed input and output schemas. The server supports the current 2026-07-28 discovery flow and the standard 2025-11-25, 2025-06-18, and 2025-03-26initialize handshakes used by existing clients. Server metadata is published at /.well-known/mcp.json using the official MCP Registry server schema.
CLI
There is no portfolio-specific CLI to install. The public surface is one read-only JSON fetch, so curl and any OpenAPI client already cover it without another package or update channel. An official npm, PyPI, or Homebrew CLI will make sense if the API grows into multiple authenticated or write operations.