Query across all your customer data

llm prompts Build a global search bar Pick the right token per call

The same two endpoints called with your provisioning token run organisation-wide: the per-customer isolation filter is dropped, so retrieval spans every API account's index plus your organisation-level content in one search.

Example: a marketplace with many sellers offering one global search across the whole platform: each seller's own storefront widget queries with their token, while the marketplace's global search bar queries with the provisioning token.

GET /question behaves the same way: swap the token and one answer is grounded across the whole fleet, citations included.

Add response_format=structured to either endpoint to receive the same opt-in schema used by customer-scoped queries: top-level format, query, markdown, and results; each result contains content, position, rank, score, content_sha, and sources; and each source contains citation, uid, title, url, source_updated_at, and connection. The provisioning token changes the retrieval scope, not the response shape. If response_format is absent or has any value other than structured, each endpoint keeps its existing default response.

Reads only

Writes are refused in this mode. Saving a namespace with a provisioning token answers 403:

{ "error": "The provisioning token is read-only on this endpoint. Save with an api_account query token." }

An organisation-wide memory write would be fleet-visible with no sensible owner, so save with a customer token instead and the note lands in exactly one customer's index.

A provisioning token stops authenticating the moment it stops being eligible: the holder is demoted from admin, or the organisation leaves the white-label plan. It does not degrade into a normal user-scoped credential.

curl "https://context-link.ai/api/v1/context?query=hand-thrown+ceramics" \
  -H "Authorization: Bearer $PROVISIONING_TOKEN"

require "net/http"

uri = URI("https://context-link.ai/api/v1/context")
uri.query = URI.encode_www_form("query" => "hand-thrown ceramics")

request = Net::HTTP::Get.new(uri)
request["Authorization"] = "Bearer #{ENV.fetch("PROVISIONING_TOKEN")}"

response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: uri.scheme == "https") do |http|
  http.request(request)
end

puts response.body

import os
import requests

url = "https://context-link.ai/api/v1/context"
params = {"query": "hand-thrown ceramics"}

headers = {
    "Authorization": f"Bearer {os.environ['PROVISIONING_TOKEN']}",
}

response = requests.get(url, headers=headers, params=params, timeout=30)
print(response.text)

// Runs on your server only: the token must never reach the browser.
const url = new URL("https://context-link.ai/api/v1/context");
url.searchParams.set("query", "hand-thrown ceramics");

const response = await fetch(url, {
  method: "GET",
  headers: {
    "Authorization": `Bearer ${process.env.PROVISIONING_TOKEN}`,
  },
});

console.log(await response.text());

// Runs on your server only: the token must never reach the browser.
async function main() {
  const url = new URL("https://context-link.ai/api/v1/context");
  url.searchParams.set("query", "hand-thrown ceramics");

  const response = await fetch(url, {
    method: "GET",
    headers: {
      "Authorization": `Bearer ${process.env.PROVISIONING_TOKEN}`,
    },
  });

  console.log(await response.text());
}

main();

Response

{ "message": "<markdown drawn from every customer's index plus shared organisation content>", "format": "markdown" }

← Back to Docs Raw markdown guide for AI