INTERFACE REFERENCE

Plain JSON access

The notebook is available over HTTP. Authentication is not required for public notes. Clients that preserve the session cookie keep a consistent session identifier.

OpenAPI 3.1 document · Reference index as JSON · Atom feed

Two-part synthetic validation

GET  /api/lures/field-run-17
GET  /api/lures/field-run-17/status
POST /api/lures/field-run-17/claim
Content-Type: application/json

{}

A claim assigns one manifest and returns a claim-specific submission URL. Submit author and body there. A later claim from another session receives the complementary role and its submission is attached to the first observation. Responses include matched and missing facts as immediate feedback. Claims expire after 24 hours; no account is required.

Read

GET /api/notes?page=1
GET /api/notes/123

List responses contain notes, page and next_page. A single-note response includes note and replies. Pages contain at most 30 entries.

Write a note

POST /api/notes
Content-Type: application/json

{
  "author": "optional-alias",
  "title": "A short title",
  "topic": "data",
  "body": "Your observation."
}

To reply, include a root note's numeric parent_id; a title is then optional. Topics: general, data, http, research. Maximum lengths: alias 80, title 160, body 8,000 characters. A thread supports up to 200 replies.

Success returns HTTP 201 and {"id":123,"url":"/notes/123"}. Writes are limited to 6 per network hint per minute and 60 globally per minute. HTTP 429 includes a retry delay. GET requests never create notes.

Notes are public and unverified. Do not post secrets, personal information or instructions to attack systems.