Alp Yalay Developer Portal & API
Public REST API, Model Context Protocol (MCP) server, CLI tools, and agent instructions for autonomous systems and developers.
Quickstart
All REST endpoints are publicly accessible, unauthenticated, and return typed JSON.
curl -s https://alpyalay.org/api/v1/profile | jq
curl -s 'https://alpyalay.org/api/v1/projects?lane=builder' | jq
npx alp-yalay
REST API v1 Endpoints
/api/v1/profileReturns bio, roles, location, contact methods, focus areas, key projects, and developer resources.
curl https://alpyalay.org/api/v1/profile
/api/v1/projectsList portfolio projects with optional filters: `lane` (builder | client | localization | ai-tools), `tier` (featured | supporting | archive), `q` (search query).
curl 'https://alpyalay.org/api/v1/projects?tier=featured'
/api/v1/projects/:slugRetrieves granular metadata, proof points, links, and case study excerpts for a given slug.
curl https://alpyalay.org/api/v1/projects/realdex
/api/v1/skillsReturns technical skill taxonomy, spoken/programming languages, certifications, and core domains.
curl https://alpyalay.org/api/v1/skills
/api/v1/healthReturns health status, active API version, timestamp, and documentation links.
curl https://alpyalay.org/api/v1/health
Model Context Protocol (MCP) Server
JSON-RPC 2.0 Model Context Protocol endpoint for direct tool calling by Claude Desktop, Cursor, Antigravity, and autonomous agents.
Supported methods: initialize, tools/list, tools/call, ping.
curl -X POST https://alpyalay.org/api/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_case_study",
"arguments": { "slug": "realdex" }
}
}'Rate Limits & Headers
The API is currently unthrottled — endpoints serve static data and are safe to poll. Every response still carries standard headers:
- Api-Version: 1.0.0
- Access-Control-Allow-Origin: *
- Cache-Control: public, max-age=3600
RFC 9457 Problem Details
Errors are returned with application/problem+json and structured machine-readable codes (`INVALID_SLUG`, `PROJECT_NOT_FOUND`).
Versioning follows URL pathing (`/v1/`). Deprecations are signaled via RFC Sunset headers with a 180-day grace period.