‹ Back to portfolio

PaRi Portfolio Vercel developer resources

Predictable paths for agents and tools.

Use these resources to understand, cite, and navigate the portfolio without scraping the visual interface.

Vercel developer resources

  • OpenAPI spec — typed API contract with operation IDs, request schemas, response schemas, and rate-limit headers.
  • llms.txt — agent guidance, use cases, limitations, and canonical links.
  • sitemap.xml — indexable URL inventory with last modification dates.
  • MCP manifest — read-only Streamable HTTP metadata.
  • Versioned MCP endpoint — canonical JSON-RPC tools for public portfolio and project discovery.

Named project resources

Use the case studies when you need evidence about a named product or implementation context. Each project has a stable case-study route and a linked live preview where available:

These previews are hosted on Vercel. They are not a public API, OpenAPI document, authentication flow, or webhook service.

API versioning and rate limits

PaRi Portfolio is deployed on Vercel. The canonical read-only MCP API is /api/v1/mcp. The unversioned /api/mcp path remains a compatibility alias and sends RFC 9745 Deprecation and successor Link headers.

API responses publish RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy for a 60-request, 60-second advisory window. Clients receiving 429 should honor Retry-After. The MCP endpoint is intentionally read-only and only describes public portfolio content. For identity and contact verification, use the about page, contact page, and privacy page.