API overview

Runlog as the memory behind your product: point it at a codebase or a bucket, recall from it with sources, and put agents on it, under your own key.

Credentials

An account key (rlka_) acts as you and names its project per request on X-Project-Id; a project key (rlk_) reaches one project. Mint either as on Sign in and keys. A project is the memory boundary: one per customer or per repository.

API key an rlka_ key, or an api-scoped rlk_ keySession the signed-in session; a key answers 401Site key a published site’s own key, in the bodyOpenAPI 3.0

The first call

One route dispatches every action. This one packs the code most relevant to a task, with where each piece came from.

curl

curl -X POST "https://runlogai.com/runlogapi/api/actions" \
  -H "Authorization: Bearer $RUNLOG_API_KEY" \
  -H "X-Project-Id: p7Kd2mQx" \
  -H "Content-Type: application/json" \
  -d '{"action": "code_context_pack", "input": {"task": "what does this repository do?"}}'

Pick by goal

A memory layer for a codebaseStart → Remember → Keep current · the workflow
A memory layer for a data lake or bucket (S3, GCS, any HTTPS URL; a warehouse as an export)Start → Remember → Keep current
Ask with citationsRecall · the workflow
Act on the memoryAct · the workflow

For agents

/openapi.json is the OpenAPI document. /llms-api.txt is the whole surface as plain text. Both come from the same declarations as these pages.