04 / Developers

Research, as JSON.

The Sma Das API lists, fetches, and searches public articles on sma-das.blog. GET is open. API keys are optional. Agent registration follows /auth.md.

OpenAPI auth.md llms.txt

Quickstart

First call in one request

No key is required. These URLs are the same ones the sandbox below uses.

curl https://sma-das.blog/api/v1/posts
curl "https://sma-das.blog/api/v1/search?q=enginered"
curl https://sma-das.blog/api/v1/posts/enginered-asymmetric-ai-warfare

API keys

Optional identity

Issue a key if you want a stable caller id. Send it as Authorization: Bearer sdr_live_…. Invalid tokens get HTTP 401 with a WWW-Authenticate hint pointing at the protected-resource metadata. Public GET still works with no header.

Sandbox

Live search

This form hits GET /api/v1/search on this origin. It is the sandbox environment for the research API.

Try a title fragment or a tag. The response is the same JSON an agent gets from GET /api/v1/search.

Documentation

Endpoints

GET /api/v1Index of documentation, OpenAPI, and auth.
GET /api/v1/postsPublished catalog. Optional limit query.
GET /api/v1/posts/{slug}One article plus its markdown body.
GET /api/v1/search?q=Keyword search over title, tags, and description.
POST /api/v1/keysSelf-serve API key. JSON or form body with optional label.

Machine-readable contract: /openapi.json. Agent registration: /auth.md. Discovery: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.