For platforms
Put a permission-aware memory layer inside your product, under your own name
Your customers are companies, and each of them has systems of record your AI features need to read. Contextely gives you one API call per client: a workspace, the people inside it, and a key per person whose answers are already filtered by who is asking.
What white-label means here, and what it does not
Your product's name on it, your API key, your billing relationship, your support queue. Your customers never see a Contextely login, a Contextely URL or a Contextely invoice, because there is nothing for them to see: the integration is server to server.
It does not mean a themed Contextely dashboard handed to your customers, and it does not mean a custom domain. If what you want is our screens with your logo on them, this is the wrong product, and we would rather say so on this page than in month three.
The whole integration
Four calls. The first three are idempotent, so you can run them on every one of your customer's logins rather than tracking what you have already created.
Create a client
# 1. A new client signs up in your product. Idempotent on external_ref,
# so you can call this on every one of their logins.
curl -s https://www.contextely.com/api/v1/org/tenants \
-H "Authorization: Bearer ctx_org_..." \
-H "Content-Type: application/json" \
-d '{"external_ref":"cust_8812","name":"Acme Ltd","query_cap":25000}'Create a person and mint their key
# 2. One person inside that client. `scopes` is whatever your own
# permission model says they may see.
curl -s https://www.contextely.com/api/v1/org/tenants/$TENANT/members \
-H "Authorization: Bearer ctx_org_..." \
-H "Content-Type: application/json" \
-d '{"email":"priya@acme.example","role":"member","scopes":["finance:*"]}'
# 3. A key that speaks as exactly that person. Shown once. You store it.
curl -s https://www.contextely.com/api/v1/org/tenants/$TENANT/keys \
-H "Authorization: Bearer ctx_org_..." \
-H "Content-Type: application/json" \
-d '{"member_id":"'$MEMBER'"}'Retrieve on their behalf
# 4. From here it is the ordinary product. This answer is scored
# against Priya's entitlement, not against your key's.
curl -s https://www.contextely.com/api/v1/search \
-H "Authorization: Bearer ctx_sk_..." \
-H "Content-Type: application/json" \
-d '{"query":"acme renewal date"}'Pooled usage
curl -s https://www.contextely.com/api/v1/org/usage \ -H "Authorization: Bearer ctx_org_..."
The part you would not want to build
Inside each of your clients, different people may see different things. Contextely applies that inside the ranking function itself: an object the asker may not see scores exactly zero and leaves with the irrelevant ones. There is no redaction pass, and no model is ever handed a record the reader is not entitled to.
Your client's finance lead and your client's intern get different answers to the same question, and you did not build it. How the entitlement model works.
People & scopes
One bill, pooled across every client
$499
per month
25 clients- 250,000 retrievals and 40,000 staleness refreshes a month, pooled across every client rather than fixed per client.
- Past that, $1.20 per 1,000 retrievals and $12.50 per 1,000 refreshes. It bills and keeps serving.
- Every client gets the full Contextely Pro capability set, because that is what you are reselling.
- A cap per client that you set, so one of them cannot spend the rest.
That is about what 10 Contextely Pro subscriptions cost, for the same volume. Below 10 clients you are better off buying the subscriptions, and we would rather you did. See the other plans.
Who does what
| Tier-one support for your customers | You |
| Setting each client's cap and pricing them | You |
| Provisioning clients, people and keys | You, through the API |
| The entitlement engine and the freshness contract | Us |
| Condensation cost and the model bill | Us |
| Operating and scaling the hosted service | Us |
Licence and terms
Self-hosting Contextely is free for your own company's internal use, with no limits and no licence check. Running it for your own customers, or presenting it under another name, is what this arrangement covers, because that is where the support and the operating cost land on us rather than on you.
The agreement is the Contextely Partner Agreement v1, sent on request. It defines a retrieval and a staleness refresh by what the software actually counts, so an invoice and the contract cannot mean different things by the same word, and the prices in it are checked against the prices the product charges by a test rather than by anyone remembering.
Nothing in the codebase checks any of it: the licence is a promise rather than a lock, and we would rather it stayed that way. More on self-hosting.
Questions people actually ask
Do my customers ever see Contextely?
No. The integration is server to server: your backend calls our API and your product renders the answer. There is no Contextely login, URL or invoice for them to see, and no email is ever sent to them from us. That last one is enforced by a test, because it is the sort of thing one shared code path away from happening by accident.
How is a client's data kept apart from another client's?
Every client is its own workspace, and a workspace is the tenant boundary for every row and every query. On top of that, an organization key can only ever name a workspace it owns: asking for somebody else's answers not_found, the same as asking for one that does not exist, because a distinguishable refusal would tell you which of your competitors is also a customer.
What stops one client spending everything?
You set a cap per client, and raising it takes effect on their very next request. The pooled allowance behaves differently on purpose: past it, usage bills as overage and keeps serving. A hard stop at the included volume would turn a billing event into a simultaneous outage across every client you have.
Can I see my clients' memory to debug a problem?
Not from the partner console, and that is deliberate. Your staff are not members of your clients' workspaces. When you need to debug, mint a key for a person inside that client and use it, which leaves an entry in that client's own audit log. We would rather give you the accountable path than the convenient one.
I only have a handful of clients. Is this worth it?
Probably not yet. $499 is about what ten Contextely Pro subscriptions cost, and below that the subscriptions are cheaper. What this tier sells is the thing Pro structurally cannot do: one bill, one credential, and a client provisioned in a single API call. Buy it when the provisioning is the problem, not when the volume is.