Four Steps to Live
Sign up with your organization name, grab the Organization API Key we provision for you, then make your first bot call. No long setup, and no sales call required to start.
- Create Your WorkspaceRegister with an organization name and Knowledge Spaces creates your initial workspace.
- Connect a Model KeyFree access runs on your provider key. Add OpenAI, Anthropic, Gemini, DeepSeek, or another supported model.
- Get Your Org KeyWe create your organization and provision its API Key. Copy it from your console, keep it in your secret store, and regenerate it at any time.
- Go LiveMove to paid usage when you need higher limits, managed models, or production support.
Talk to a Bot in One Call
Connect a model provider key, generate your Organization API Key, then point it at a bot and get an answer grounded in your content.
SESSION_ID="$(uuidgen)" # one new UUID per conversation
curl -X POST https://spaces.sprinklenet.com/api/bots/<bot_id>/chat \
-H "Content-Type: application/json" \
-H "X-API-Key: ks_live_••••••••" \
-d '{ "session_id": "'"$SESSION_ID"'",
"text": "What is our refund policy?" }'
const sessionId = crypto.randomUUID(); // one per conversation
const res = await fetch(
"https://spaces.sprinklenet.com/api/bots/<bot_id>/chat",
{
method: "POST",
headers: {
"X-API-Key": "ks_live_••••••••",
"Content-Type": "application/json",
},
body: JSON.stringify({
session_id: sessionId,
text: "What is our refund policy?",
}),
}
);
const data = await res.json();
console.log(data.text.content);
import uuid
import requests
session_id = str(uuid.uuid4()) # one per conversation
res = requests.post(
"https://spaces.sprinklenet.com/api/bots/<bot_id>/chat",
headers={"X-API-Key": "ks_live_••••••••"},
json={"session_id": session_id, "text": "What is our refund policy?"},
)
print(res.json()["text"]["content"])
One Platform, Many Tenants
Your account starts with an organization workspace. As you grow, managed organizations can separate bots, knowledge spaces, and data by customer, brand, or environment.
Organization keys, rate limits, sessions, and bots are scoped by organization, so one customer can never reach another's data.
Principal Organization and Tenants
Platform Capabilities
Everything you need to run AI knowledge agents for many tenants in production.
Tenant Isolation
Organizations and managed child organizations keep each customer's data, bots, and spaces isolated.
Organization API Key
One hashed organization key for bot chat and session APIs. Regenerate it in Account Settings when access needs to rotate.
Session APIs
Create, continue, inspect, update, end, and delete conversation sessions through the public API.
Usage Controls
Track answer usage by organization and bot. Plans scale from free BYOK to managed model access.
Your Models or Ours
Bring your own OpenAI, Anthropic, Gemini, DeepSeek, or AWS-connected model access, or run on managed models.
Governance on Every Call
Every call is tenant-scoped, retrieval-bounded, and logged. It is the same control layer documented in our security white paper.
Knowledge Agents for Any Audience
Ground answers in your own content and serve a different assistant to each customer, team, or product.
Customer Support Agents
Answer from your help center, docs, and policies, with one isolated workspace per customer.
Internal Knowledge Assistants
Answer from runbooks, wikis, and handbooks, with each team's assistant scoped to its own Spaces.
Product and Docs Q&A
Embed an assistant grounded in your documentation, in your app or your site.
Working Examples
Two end-to-end walkthroughs, checked against the OpenAPI spec. Each one goes from zero to a working call, with the response you should see and the fix for the most common failure.
Your First Governed Chat Call in Five Minutes
Register, generate your Organization API Key in the console, and get a bot answer with your organization's governance (tenant isolation, logged calls) applied automatically.
1. Register and Generate Your Key
Sign up at spaces.sprinklenet.com/register with your organization name to create your workspace, then open Account Settings in the console, find Organization API Key, and select Regenerate Key (or Generate API Key if no key is set) to view your key. The full key is shown only once, so store it in a secret manager now. Regenerating replaces the previous key immediately.
export KS_API_KEY="ks_live_your_key_here"
export BOT_ID="665f1a2b3c4d5e6f7a8b9c0d" # from your bot in the console
2. Call the Bot
One POST with a session_id you control and the user's text.
curl -X POST "https://spaces.sprinklenet.com/api/bots/$BOT_ID/chat" \
-H "Content-Type: application/json" \
-H "X-API-Key: $KS_API_KEY" \
-d '{ "session_id": "'"$(uuidgen)"'", "text": "What should I read first?" }'
200 OK { "success": true, "text": { "content": "Start with the implementation brief...", "resources": [], "isComplete": true } }
That call ran with your org's governance applied: the key is scoped to a single organization, so it can only reach bots and sessions your org owns, and the call is tenant-scoped and logged. The answer is in text.content. Want tokens as they generate? Add "stream": true and the response becomes a text/event-stream of Server-Sent Events.
3. Read the Rate-Limit Headers
Every response carries RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset, and a 429 carries Retry-After. Read your limits from these headers rather than hard-coding them, and back off on 429. GET /rate-limit/info returns the published policy without authentication.
401 { "message": "Invalid API key" }
The key is missing, truncated, or under the wrong header. Send the full ks_live_... value as X-API-Key (or Authorization: Bearer). A key that was regenerated or revoked also returns 401. Lost keys can't be recovered (only a hash is stored); regenerate in Account Settings.
404 { "message": "Bot not found" }
The bot ID is wrong, or the bot belongs to a different organization than the key. A key only reaches bots its own organization owns, which is the isolation working as designed. Re-copy the bot ID from the console and confirm the key comes from the same organization.
Sessions That Persist
Keep one conversation across many calls, then read the transcript and manage the session's lifecycle.
1. Mint an Unguessable Session ID
session_id is caller-controlled: reuse a value to continue a thread, use a new value to start fresh. A predictable id (an email, a row number) risks one user's messages landing in another user's thread inside your product, so mint a UUID per conversation.
const sessionId = crypto.randomUUID();
// e.g. "6b3f2c9e-8a41-4d2f-9c57-1e2a7b3d4f80"
2. Chat, Then Chat Again With the Same ID
The second call answers with the earlier turns in context.
const BASE = "https://spaces.sprinklenet.com/api";
const headers = {
"X-API-Key": process.env.KS_API_KEY,
"Content-Type": "application/json",
};
await fetch(`${BASE}/bots/${process.env.BOT_ID}/chat`, {
method: "POST",
headers,
body: JSON.stringify({
session_id: sessionId,
text: "My name is Dana. Which plan fits a two-person team?",
}),
});
const followUp = await fetch(`${BASE}/bots/${process.env.BOT_ID}/chat`, {
method: "POST",
headers,
body: JSON.stringify({ session_id: sessionId, text: "What was my name again?" }),
});
console.log(await followUp.json());
// { "success": true, "text": { "content": "You said your name is Dana.", ... } }
3. Retrieve the Transcript
Returns the 10 most recent messages in the session, oldest first. Each message carries role, text, resources, and createdAt; ignore fields you do not use.
const history = await fetch(
`${BASE}/bots/${process.env.BOT_ID}/chat?session_id=${sessionId}`,
{ headers: { "X-API-Key": process.env.KS_API_KEY } }
);
console.log(await history.json());
200 OK { "success": true, "messages": [ { "role": "user", "text": "My name is Dana. Which plan...", "createdAt": "2026-07-08T14:03:12.000Z" }, { "role": "assistant", "text": "For a two-person team...", "createdAt": "2026-07-08T14:03:14.000Z" } ] }
4. Inspect and Manage the Session
GET /sessions/{session_id} returns the record: session_id, chatbot_id, created_at, last_active_at, message_count, status. Attach your own metadata with PUT /sessions/{session_id}/context, close with POST /sessions/{session_id}/end (transcript retained), or erase entirely with DELETE /sessions/{session_id} for GDPR erasure requests.
curl -X PUT "https://spaces.sprinklenet.com/api/sessions/$SESSION_ID/context" \
-H "Content-Type: application/json" \
-H "X-API-Key: $KS_API_KEY" \
-d '{ "end_user_id": "user_42", "custom_context": { "plan": "enterprise" } }'
404 Not Found on GET /sessions/{session_id}
Sessions are created by the first chat call that uses the id; there's no separate "create session" step. Send at least one chat message with that session_id first, and check the id in the URL matches the one you chatted with exactly.
Control the Data Plane as You Grow
BYOK is available today. Customer storage and private model endpoints are Enterprise architecture options, not free-tier toggles.
Customer Storage Review
Enterprise deployments can evaluate customer-controlled object storage, region selection, encryption policy, and retention requirements.
Private Model Endpoints
For regulated teams, we can scope OpenAI-compatible private endpoints, customer cloud models, and egress controls as part of Enterprise setup.
Governed Rollout
Storage and private-model controls affect support, billing, security, and incident response, so they are configured through a managed Enterprise workflow.
Knowledge Spaces
Applications
Governance
Delivery
Advisory
Industries
Government and Teaming
Company
Contact
Contact
Scope a Six-Week Pilot