Machine-readable portfolio
Developer documentation
These interfaces help agents and developer tools evaluate Nicolay Camacho's public professional profile and portfolio. They require no account or API key, expose public information only, and do not provide write actions.
Public resources
- Discovery guide
Human- and agent-readable index of public site content.
- OpenAPI 3.1
Typed HTTP operations, success envelopes, and problem responses.
- Profile JSON
Professional focus, stack, location, and contact guidance.
- Projects JSON
Project summaries, technical evidence, and case-study links.
- MCP registry
Registry-format discovery manifest for the MCP server.
- MCP server card
Canonical identity, transport, version, and endpoint metadata.
- Agent manifest
Consolidated capabilities, resources, and access boundaries.
Quick start
Start with /llms.txt for routing, use /openapi.json for typed HTTP calls, or initialize the MCP endpoint at /api/mcp. The MCP server supports get_profile, get_projects, get_experience, and get_contact. Every tool is read-only and accepts no arguments.
curl -H 'Accept: application/json' \
https://nicolaycamacho.com/api/profile.jsonErrors and boundaries
Unsupported HTTP API paths return a real 404 with an RFC 9457-style application/problem+json body. Invalid MCP calls return structured JSON-RPC errors with a stable code and a resolution hint. There is no hidden authenticated API, mutation surface, billing account, or sandbox environment behind this documentation.
← Home · Agent guide · Privacy