lobo.sh
Machine & Developer Interfaces

lobo.sh Developer Portal & API

lobo.sh provides first-class programmatic interfaces designed for software engineers, automated tool execution, and autonomous AI agents.

OpenAPI 3.1.0 Spec (JSON)
/openapi.json →
OpenAPI YAML Spec
/api/openapi.yaml →
Agent Guidelines
/agent-instructions.md →
LLM Context Manifest
/llms.txt →

lobo.sh API Quickstart (curl)

You can test the public endpoints directly from your terminal or script:

# Check service operational health and version
curl -s -i https://lobo.sh/api/v1/health
# Fetch author profile and focus
curl -s https://lobo.sh/api/v1/profile
# Query markdown content representation
curl -s -H "Accept: text/markdown" https://lobo.sh/

lobo.sh API Authentication & Rate Limit Policy

  • Authentication: All read-only endpoints are completely public. No API keys, Bearer tokens, or registration are required.
  • CORS: Cross-Origin Resource Sharing is enabled (Access-Control-Allow-Origin: *) across all API routes to allow browser execution and agent sandboxes.
  • Rate Limiting: Fair-use threshold of 60 requests per minute per IP client.
  • RFC Rate Limit Headers: All responses broadcast real-time throttling metadata so AI agents can self-throttle:
    • RateLimit-Limit: 60 — Total quota per minute window
    • RateLimit-Remaining: 59 — Remaining calls in active window
    • RateLimit-Reset: 60 — Seconds until window quota resets
    • RateLimit-Policy: 60;w=60 — Window specification
  • Throttling Recovery (HTTP 429): If the quota is exceeded, the server responds with HTTP 429 (Too Many Requests) including a Retry-After header specifying the required backoff in seconds.
  • Structured Errors: Failed requests return structured JSON payloads with machine-readable error codes and recovery hints (status 4xx/5xx).

lobo.sh API Versioning & Deprecation Policy

lobo.sh enforces strict stability contracts to ensure autonomous agents and integrations never break unexpectedly:

  • Path-Based Versioning: API routes are explicitly versioned in the URI path (e.g. /api/v1/...). Active version is v1.
  • Version Broadcast: Every API response emits API-Version: 1.0.0 and X-API-Version: 1.0.0 headers.
  • Deprecation Signaling: When an endpoint or version is marked for deprecation, it will broadcast standard IETF headers:
    • Deprecation: @<timestamp> (RFC 9594) — Declaring deprecation date
    • Sunset: <HTTP-date> (RFC 8594) — Declaring final decommission timestamp
  • 12-Month Sunset Window: Any announced deprecation guarantees a minimum migration timeline of 12 months before service retirement.

lobo.sh Public REST API Reference & Endpoints

GET /api/v1/health

Check service operational health, version, deprecation status, and discoverable endpoints.

curl -s https://lobo.sh/api/v1/health
GET /api/v1/profile

Retrieve author profile, engineering focus areas, and verified contact links.

curl -s https://lobo.sh/api/v1/profile
GET /api/v1/essays

List published technical essays with summaries, slugs, and language tags.

curl -s https://lobo.sh/api/v1/essays
GET /api/v1/essays/{slug}

Fetch the full content, metadata, and canonical links of an essay by slug.

curl -s https://lobo.sh/api/v1/essays/architecture-decisions
GET /api/v1/search

Search site index, essays, and architectural principles.

curl -s https://lobo.sh/api/v1/search

lobo.sh Markdown Content Negotiation (acceptmarkdown.com)

Every webpage on lobo.sh advertises an alternate markdown representation. AI agents and scrapers can request raw Markdown directly by sending: 

Accept: text/markdown

Or by appending .md to canonical URLs:

← Back to home view raw markdown