Enterprise evaluation
When support learns something new, operations needs the accepted update and its source. Evaluate shared customer records, conflict rules, and review in one focused pilot with your team.
Managed service · hosted REST API · hosted MCP · TypeScript SDK preview
Customer / sample_1042
From proposal to accepted state
Follow a sample customer update through field checks and review. The example uses a configured policy and illustrates the workflow; it is not a customer result.
A structured import established the customer’s contact channel. Both agents use the same customer ID.
Both agents read the same accepted record.
customer:sample_1042An allowed value with nothing to conflict with
09:00 UTC · source: customer-import · confidence: 1.00
The application supplies structured proposals; no prebuilt support-system connector is assumed. Enforcement and review must be configured for the fields you choose.
Set expectations before integration
Available means implemented in the managed-service interfaces. Pilot-only means agreed evaluation work. Planned capabilities carry no delivery date.
| Capability | Status | Evaluation boundary |
|---|---|---|
| Hosted REST API and MCP | Available | Propose changes, read current records and inspect history in the managed service. |
| Field constraints and review | Available | Opt-in enforcement and review policies. Review decisions are available to authorized writers; a human-only approval role is not enforced. |
| Current state, history and provenance | Available | Read accepted facts separately from superseded or disputed values and inspect change records. |
| Resumable write operations | Available | Plans of 1–50 observations with an idempotency key and receipts. Each observation commits separately; a plan is not one atomic transaction. |
| Guided support-context evaluation | Pilot-only | A jointly scoped workflow, integration assistance and outcome measurement, subject to an agreed pilot brief. |
| Public TypeScript SDK release | Planned | The client implementation and preview documentation exist. Public npm publication is pending. |
| Provider keys or corporate model endpoints in ConceptMem | Planned | Not available in the service today. Your application can use its own model and submit structured observations. |
Integration references: hosted MCP · TypeScript SDK preview. Ontology rules execute inside the managed service.
Security & reliability
These describe implemented service behavior. Agree the operational requirements for your workload before making it a production dependency.
Session access checks workspace membership. Owner and editor roles can write; viewers cannot. Workspace API keys are stored as hashes and can be revoked.
API keys carry agent authority. Human schema authority comes from authenticated user access.
Each observation runs in a database transaction. PostgreSQL serializes governed writes within a workspace. Schema proposals can reject a stale expected revision.
Rate limits return a retry interval. Request allowances are limits, not throughput guarantees.
Accepted mutations carry source, actor, confidence, timestamp and extraction method. Current facts and their history are separate; review decisions include decision context.
Exports are views of state. They are not a full restorable backup.
Start with synthetic or minimized data. Confirm data scope, access, any use of hosted AI, support hours and an exit procedure in the pilot brief. The listed plans do not include dedicated compute or a contractual uptime SLA.
A focused pilot
Choose the changing fields that create work for your team. Agree scope, capacity, support, and success criteria, then measure whether shared records improve the workflow.
Usage, support & purchasing
Capacity is shared across databases owned by an account. See pricing for the full catalog and Billing & usage to review a plan after sign-in.
| Plan | Monthly price | Operations / month | Support |
|---|---|---|---|
| Free | US$0 | 5,000 | Self-service |
| Build | US$49 | 250,000 | Standard asynchronous support |
| Growth | US$149 | 1,000,000 | Priority during business hours |
| Scale | US$399 | 3,000,000 | Priority support + one initial architecture session |
A query or mutation call counts once; a batch counts each submitted observation. Invalid requests that reach execution may count. Exports, MCP handshakes, static catalogs and account administration are excluded. The operation allowance resets at the start of each UTC month.
Storage includes data, provenance, history and indexes. Archived databases still count. Storage limits can block writes; the monthly operation limit pauses data operations. Export remains available. Rate limits are separate and apply across the account.
Review Free, Build, Growth or Scale in Billing & usage. Enterprise capacity and support are discussed through contact, not a separate self-service checkout tier. Confirm business hours, response targets and pilot fees before agreement.
Managed AI is presented separately from database operations in pricing; confirm the model and workload requirements when scoping the pilot.
Enterprise pilot
Bring one recurring support or operations workflow. We’ll use it to scope the integration, update rules, and measures of success.