Skip to content
CLCarter LaSalle
AboutExperienceProjectsResearchBlogFilmsFingerprintContact

Opening record…

End of file / keep in touch

Carter LaSalle
GitHubLinkedInBlogFilmsFingerprintDevelopers

© 2026 Carter LaSalle. All rights reserved.

APIs / machine access

Developer Portal

API documentation, authentication guides, and agent resources for integrating with the Carter LaSalle portfolio.

Quick Start

Get started with the portfolio API in minutes. All endpoints are publicly accessible for read operations.

API Documentation

Complete OpenAPI 3.1 specification with endpoints, schemas, and examples.

OpenAPI Spec

Machine-readable API specification for code generation and tooling.

API Endpoints

GET/api/status

Check API availability and health status. Returns JSON with status and service fields.

POST/api/contact

Send a message through the portfolio contact form. Requires same-origin requests, rate limited to 5 requests per hour.

POST/mcp

Model Context Protocol server (JSON-RPC 2.0 over Streamable HTTP). Exposes portfolio profile data as MCP tools.

Authentication

The portfolio API uses same-origin validation for the contact endpoint. No API keys are required for public read operations.

Same-Origin Policy

The /api/contact endpoint validates the Origin header to ensure requests originate from the portfolio domain. Cross-origin requests will receive a 403 response.

Rate Limiting

API endpoints are rate limited to prevent abuse. Rate limit headers are included in all responses.

Response Headers

  • RateLimit-Limit — Maximum requests per window
  • RateLimit-Remaining — Requests remaining in window
  • RateLimit-Reset — Unix timestamp when window resets
  • Retry-After — Seconds until retry (on 429 responses)

Agent Integration

The portfolio provides machine-readable endpoints for AI agent integration.

llms.txt

Concise machine-readable index for AI agents and language models.

llms-full.txt

Expanded profile with project details and citation guidance.

MCP Manifest

Model Context Protocol server manifest for tool integration.

API Catalog

RFC 9727 linkset for API discovery and service description.

Error Handling

All error responses include structured JSON with machine-readable error codes and resolution hints.

{
  "success": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Name must be between 2 and 100 characters.",
    "resolution": "Check the request body fields match the required schema"
  }
}

Support

For API support or questions, contact carterlasalle@gmail.com or use the contact form.