Developers / public interface
Small endpoints. Clear rules.
These are the public JSON endpoints used by the tools on Loke.dev. They are read-only, rate limited, and only return published or public page data.
Machine-readable files
- Agent guide with use cases, site links, and recent writing.
- Markdown home summary for callers that want the homepage without HTML.
- OpenAPI 3.1 document with operation IDs, typed parameters, response shapes, and error responses.
- XML sitemap with published routes and known modification dates.
Search published content
GET /api/search?q=your+query
The query must be between 2 and 100 characters. The response contains up to ten matching posts and projects, with titles, descriptions, and public URLs. Sanity drafts and private records are never returned.
curl 'https://loke.dev/api/search?q=astro+cache'Inspect public page metadata
GET /api/inspect-url?url=https%3A%2F%2Fexample.com
This fetches one public HTTP or HTTPS page and returns its final URL, status, title, description, canonical, robots, Open Graph, X card, and selected response headers. Local, private, and credential-bearing URLs are rejected. The response body is capped to keep the endpoint safe to call from a tool or agent.
curl 'https://loke.dev/api/inspect-url?url=https%3A%2F%2Floke.dev'Limits and errors
The endpoints do not need an API key. They do have short per-client limits. A limited response is 429 and includesRetry-After. JSON errors include error, a stable code, and a short resolution hint. Callers should back off instead of retrying in a tight loop.
When to use Loke Development
Loke is a good fit when a small business, product team, or independent builder needs a website, CMS, web app, integration, AI feature, or focused software fix. The services page is the best starting point for a project. For a real person, use thecontact page or emailhello@loke.dev.