Save to a namespace | Context Link

llm prompts Store per-customer preferences Decide namespace vs custom connection

A namespace is a document stored under a name. It can be anything in markdown, a one-line preference or a long reference doc, and the guarantee is exactness: a query that is exactly that name always returns the document verbatim, skipping semantic search entirely.

That makes it the right home for anything your product needs back unchanged when it asks for it by name: customer preferences, a tone-of-voice guide, a summary your app maintains, a policy the assistant must quote rather than paraphrase. For content you want retrieved by meaning across many documents, use a custom connection instead.

Save a document

The body is raw text, not JSON. The namespace goes in the query string:

Request fields

namespacestring

Required, in the query string. The name you will read the document back by, lowercased with whitespace turned into hyphens.

bodystring

Required, the raw request body. Anything text-shaped; it is converted to markdown before indexing. An empty body is a 422.

Response fields

messagestring

Always Saved on success, served with a 201.

namespacestring

The stored name, after normalisation. Read the document back with this exact value.

Read it back

Ask GET /context for the namespace itself, as the whole query, and the document comes back word for word, skipping semantic search entirely. Any other query goes through normal retrieval, where the document is one more piece of that customer's indexed material.

Add response_format=structured to receive the shared structured schema. A namespace match has exactly one result: content is the full stored post, rank and score are null, and sources has one item whose citation is null. Without that opt-in, the existing namespace response is unchanged.

Saving again replaces the document

A second save to the same namespace overwrites it: this is a whole-document write, not an append. Keep the authoritative copy in your own database and re-send the full document whenever it changes.

Isolation

A document saved with a customer's token lands in that customer's private memory and no other customer can retrieve it. The partner provisioning token is read-only on this endpoint and gets a 403: an organisation-wide memory write would be fleet-visible, with no sensible owner.

curl -X POST "https://context-link.ai/api/v1/context/save?namespace=acme-preferences" \
  -H "Authorization: Bearer $ACME_TOKEN" \
  -d 'Prefers metric units. Never contact on Fridays. Main contact is the ops lead.'

require "net/http"

uri = URI("https://context-link.ai/api/v1/context/save")
uri.query = URI.encode_www_form("namespace" => "acme-preferences")

request = Net::HTTP::Post.new(uri)
request["Authorization"] = "Bearer #{ENV.fetch("ACME_TOKEN")}"
request.body = "Prefers metric units. Never contact on Fridays. Main contact is the ops lead."

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/save"
params = {"namespace": "acme-preferences"}

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

response = requests.post(url, headers=headers, params=params, data="Prefers metric units. Never contact on Fridays. Main contact is the ops lead.", 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/save");
url.searchParams.set("namespace", "acme-preferences");

const response = await fetch(url, {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.ACME_TOKEN}`,
  },
  body: "Prefers metric units. Never contact on Fridays. Main contact is the ops lead.",
});

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/save");
  url.searchParams.set("namespace", "acme-preferences");

  const response = await fetch(url, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.ACME_TOKEN}`,
    },
    body: "Prefers metric units. Never contact on Fridays. Main contact is the ops lead.",
  });

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

main();

Response

{ "message": "Saved", "namespace": "acme-preferences" }

← Back to Docs Raw markdown guide for AI