For engineers

Keeplore API docs

Last updated 24 October 2026

The API has two endpoints. POST /api/v1/query takes a question and returns an answer plus the approved rules behind it. GET /api/v1/export returns every approved rule. Both use JSON over HTTPS and one API key.

Only rules a manager has approved are ever returned. If no approved rule applies, the answer is empty. When a rule does apply, a model writes a short answer from the approved rules, and the rules it used come back with it.

Base URL: https://keeplore.dev/api/v1.

Authentication

Send an API key in the Authorization header. Keys start with lore_. A company admin creates a key in the Keeplore dashboard under API keys: give it a name and copy it straight away. Keeplore stores only a hash of the key, so it cannot show it again. An admin can revoke a key from the same page, and a revoked key returns 401.

Authorization: Bearer lore_...

POST /api/v1/query

Ask a question in plain language. Keeplore picks the approved rules that apply and writes a short answer from them.

Request

Send JSON with one field. question is a string of 3 to 2,000 characters after trimming.

curl https://keeplore.dev/api/v1/query \
  -H "Authorization: Bearer $LORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question": "A customer disputed an invoice. What do we do?"}'

const res = await fetch("https://keeplore.dev/api/v1/query", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LORE_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ question: "A customer disputed an invoice. What do we do?" }),
});
const { answer, rules } = await res.json();

Response: 200

{
  "answer": "Issue the credit, then close the ticket.",
  "rules": [
    {
      "id": "0b6f3c1e-0000-4000-8000-000000000001",
      "topic": "Billing",
      "condition": "A customer disputes an invoice",
      "rule": "Issue the credit note before closing the ticket",
      "reason": "Closed tickets cannot be reopened by the billing system",
      "source": "Maya Chen, Billing lead",
      "confidence": 0.9
    }
  ]
}

When no approved rule applies

The request still succeeds. You get an empty answer and no rules, so your agent can tell "no rule" apart from an error and treat it as "hand over to a person".

{ "answer": "", "rules": [] }

GET /api/v1/export

Returns every approved rule in your company, ordered by topic and then by when it was created. Use it to load the knowledge into your own system prompt or retrieval setup.

curl https://keeplore.dev/api/v1/export -H "Authorization: Bearer $LORE_API_KEY"
curl "https://keeplore.dev/api/v1/export?format=md" -H "Authorization: Bearer $LORE_API_KEY"

format=md returns Markdown. Any other value, or none, returns JSON.

JSON response: 200

{
  "rules": [
    {
      "id": "0b6f3c1e-0000-4000-8000-000000000001",
      "topic": "Billing",
      "condition": "A customer disputes an invoice",
      "action": "Issue the credit note before closing the ticket",
      "reason": "Closed tickets cannot be reopened by the billing system",
      "confidence": 0.9,
      "source": "Maya Chen",
      "role": "Billing lead",
      "updatedAt": "2026-10-24T09:00:00.000Z"
    }
  ]
}

The export uses action where the query response uses rule, and it splits the person into source (name) and role. confidence is not rounded. reason can be null.

Markdown response: 200

The content type is text/markdown. Rules are grouped under a heading per topic.

# Company knowledge

## Billing

- **When** A customer disputes an invoice: Issue the credit note before closing the ticket *Because Closed tickets cannot be reopened by the billing system.* (Source: Maya Chen, Billing lead)

Errors

Errors are JSON with one field: { "error": "..." }.

Rate limits

Each API key can make 60 queries per minute. Once a key has made 60 queries in the last minute, requests to either endpoint return 429 until older queries fall out of that minute. Export requests are not counted. There are no other per-request limits in the API today. Each workspace also has a monthly AI allowance (the 402 error), which Keeplore staff can change.

What the API does not do

• It does not return the exact quote a rule came from. The quote is checked when the rule is extracted and is shown to the reviewer in Keeplore.
• It does not return rules that are pending or rejected.
• It does not write: there is no endpoint to create, edit or approve rules. That happens in the dashboard.
• It has no webhooks and no pagination. Export returns everything in one response.

Questions about the API? Email hello@keeplore.dev or book a demo.

Related

• Pricing The API is included for as long as you are a customer.
• Security API keys, where data is stored and who can see it.
• The query API at a glance