Start from auth, request IDs, and endpoint families.

Current reference scope

The current API reference focuses on the basics that make supportable integrations possible: auth, request context, and the core Agent API route families.

Notice

Keep request IDs and the Client context when you escalate an API issue. That is usually more useful than raw payload volume.

Issue a token first

Create a personal access token before you test any Agent API call.

1. 1

   Open `/login` and sign in with Google or magic link.

2. 2

   Go to Settings and open `Personal Access Tokens`.

3. 3

   Create a token with `read:clips` and `search:clips` when you want to test the full Agent API path.

4. 4

   Save the token immediately because the plain text value is shown only once.

Quick calls

Start with these examples before you branch into deeper integration work.

curl -sS \
  -X POST "$QUONTEXT_BASE_URL/api/v1/agent/search_context" \
  -H "Authorization: Bearer $QUONTEXT_PAT" \
  -H "Content-Type: application/json" \
  -d '{"query":"hybrid search ranking","limit":3}'

curl -sS \
  -H "Authorization: Bearer $QUONTEXT_PAT" \
  "$QUONTEXT_BASE_URL/api/v1/agent/clips/$CLIP_ID"

curl -sS \
  -H "Authorization: Bearer $QUONTEXT_PAT" \
  "$QUONTEXT_BASE_URL/api/v1/agent/recent_context?days=7&limit=5"

Related pages

Use these shortcuts when you need setup context or the broader integration view.