Starkslab
Agent SurfaceRead-only

Public Retrieval Layer

Read Starkslab in the browser. Query it from the terminal. Plug it into your agents.

Starkslab exposes a bounded public retrieval layer for published notes, published drops, cluster routing, and lower-token note sections. This surface is for retrieval only. Private and Vault layers stay outside the public contract.

Open llms.txtBrowse public notes API

First Run

Start in 60 seconds

Use one known-good public note to verify retrieval first, then widen into discovery, search, or next-read flows.

  1. 1. Open /llms.txt if your tool wants machine-readable discovery of the public routes.
  2. 2. Fetch /api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown to prove one successful retrieval immediately.
  3. 3. Move to /api/public/search when the prompt starts with query terms, or /api/public/recommend when you already have one known Starkslab page.
  4. 4. Stay inside the read-only public layer. Vault material, drafts, admin routes, and private systems are not exposed here.

Known-Good Request

This note endpoint is the fastest public retrieval check on the page.

https://starkslab.com/api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown
No authMarkdownPublished note

What is public

  • published notes
  • published drops
  • discovery clusters
  • route metadata and next reads
  • note headings and section maps

What stays private

  • Vault content
  • drafts and unpublished notes
  • admin and write APIs
  • analytics and operational telemetry

Quick Starts

Copy, paste, and verify one public note retrieval.

curl

Fastest retrieval check

curl 'https://starkslab.com/api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown'
TypeScript

Fetch markdown with the web standard

const url = "https://starkslab.com/api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown";

fetch(url)
  .then((response) => {
    if (!response.ok) throw new Error(`HTTP ${response.status}`);
    return response.text();
  })
  .then((markdown) => console.log(markdown.slice(0, 400)));
Python

Use requests against the same public note

import requests

url = "https://starkslab.com/api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown"
response = requests.get(url, timeout=20)
response.raise_for_status()
print(response.text[:400])

Entry-Point Chooser

Use the surface that matches the job.

The public routes are small on purpose. Pick discovery, direct retrieval, query-led search, or next-read recommendation based on what the agent already knows.

Discover/llms.txt

Start with llms.txt

Use this first when your tool wants machine-readable discovery before it chooses a route.

Best first step when you do not yet know which public endpoint or note slug you need.

Open /llms.txt
Retrieve/api/public/notes

Use /api/public/notes

Use note list, detail, and sections routes when you already know the note you want or need structured retrieval.

Best for direct reads, markdown exports, and lower-token section maps of published notes.

Open /api/public/notes
Search/api/public/search

Use /api/public/search

Use search when the prompt starts with keywords or a topic, not a known Starkslab slug.

Best for query-led entry when the agent needs to locate the right note or drop first.

Open /api/public/search
Next Read/api/public/recommend

Use /api/public/recommend

Use recommend after one known page to get the next likely read without rebuilding routing logic yourself.

Best when the agent already has a Starkslab slug and wants a bounded next step.

Open /api/public/recommend

Agent FAQ

Direct questions, direct answers

Can I use Starkslab with Codex or Claude Code?

Yes. The public retrieval layer is plain HTTP plus llms.txt, so any coding agent that can fetch URLs can use it.

What can an agent retrieve from Starkslab?

Published notes, published drops, discovery clusters, route metadata, and note headings or section maps from the public routes.

Is Starkslab read-only for agents?

Yes on the public contract. This surface is read-only and does not expose Vault content, drafts, admin endpoints, or write operations.

Should I start with llms.txt or the API?

Start with llms.txt when you need discovery. Go straight to /api/public/notes when you already know the note slug and want the fastest successful retrieval.

Public Routes

Compact inventory

/api/public/clusters/api/public/routes/[slug]/api/public/notes/api/public/notes/[slug]?format=markdown/api/public/notes/[slug]/sections/api/public/drops/api/public/drops/[slug]/api/public/search?q=heartbeat/api/public/recommend?from=i-read-openclaws-source-code

Query Shape

Small contract, stable fields

GET /api/public/notes?cluster=openclaw&pageRole=tutorial
GET /api/public/notes/openclaw-tutorial-mac-mini-setup
GET /api/public/notes/openclaw-tutorial-mac-mini-setup?format=markdown
GET /api/public/notes/openclaw-tutorial-mac-mini-setup/sections
GET /api/public/search?q=heartbeat
GET /api/public/recommend?from=i-read-openclaws-source-code