Docs navigation

API

Pagination

Cursor-based paging with limit and after parameters.

GET /runs, GET /instances and GET /billing/invoices are cursor-paged. Pass limit (default 25, max 100) and follow meta.next_cursor:

curl "https://lunary.cloud/api/v1/runs?limit=50" \
  -H "Authorization: Bearer lc_your_token_here"
{
  "data": [ ... ],
  "meta": { "next_cursor": "eyJrIjoxNDJ9", "limit": 50 }
}

To fetch the next page, pass the cursor back as after:

curl "https://lunary.cloud/api/v1/runs?limit=50&after=eyJrIjoxNDJ9" \
  -H "Authorization: Bearer lc_your_token_here"

Cursors are opaque: echo them back, don't parse them. A null next_cursor is the last page. A malformed cursor returns 400 invalid_cursor.

Every other list is bounded and returns its full contents in data with no meta: /catalog, /domains, /registries, /registry/images, /routines, and an instance's /hostnames and /plugs. They ignore limit and after.

Reading with an agent? This page as markdown, or the whole docs as llms.txt.