The memory and intelligence layer for AI agents. Store context, search semantically, and reason over your data — all from a single API.
API v1.0 · Base URL: https://api.bizxengine.com/v1
What is BizXEngine?
BizXEngine is a hosted memory infrastructure API. Rather than managing your own vector databases, embedding pipelines, and retrieval logic, you make a few HTTP calls and get back semantically-ranked, importance-weighted memories tailored to your agent's context.
Unlike raw RAG pipelines, BizXEngine memories carry metadata — importance scores, temporal decay, categories, and access frequency — so retrieval quality improves over time, not degrades.
Five intelligence primitives
Memory Storage
Persistent, structured memory store with TTL support and namespace isolation.
Semantic Search
Vector-based retrieval with multi-factor ranking — not just cosine similarity.
Reasoning
LLM-powered reasoning over retrieved memories. Stream results in real time.
Context Injection
Automatic deduplication and window management. Only inject what matters.
Base URL
HTTPShttps://api.bizxengine.com/v1
All API requests must use HTTPS. HTTP is not supported. Requests to the wrong scheme will receive a redirect, not a 200 response.
Request & response format
All request bodies must be JSON (Content-Type: application/json). All responses are JSON. Dates are ISO 8601 UTC strings. Amounts and IDs are strings unless noted.
All API responses include a request_id field. Include this in any support requests — it dramatically speeds up debugging.
The response returns ranked memories with relevance scores:
json — response
{"memories":[{"id":"mem_7xKzP3","text":"Client XYZ prefers async comms and morning meetings","score":0.94,"importance":8,"created_at":"2025-03-14T09:41:00Z"}],"request_id":"req_Kx8mN..."}
The score field is a composite of semantic similarity (55%), temporal recency (20%), importance (15%), and access frequency (10%) — not raw cosine distance.
A Workspace is your Business Memory Brain — an isolated namespace for a single AI agent or product. Your plan limits apply per workspace.
What is a workspace?
Every memory you write belongs to a workspace. Workspaces are fully isolated — memories in ws_sales are never returned in queries against ws_support. You can create as many workspaces as you need under a single BizXEngine account.
Your subscription plan limits (writes, retrievals, reasoning calls) apply per workspace. If you need higher limits, upgrade the workspace's plan in the dashboard.
Creating a workspace
Workspaces are created in the dashboard at app.bizxengine.com. Each workspace gets a unique ID prefixed with ws_. Pass this ID in every API call.
Store a new memory entry in a workspace. The engine automatically embeds the text, assigns importance, and classifies temporal context.
POST/v1/memory/write
Request parameters
Parameter
Type
Required
Description
workspace_id
string
REQ
Target workspace. Must belong to your account.
text
string
REQ
The memory content. Plain text, max 4,000 chars.
importance
integer
Override importance score 1–10. If omitted, the engine scores it automatically.
expires_at
string
ISO 8601 UTC. Memory decays to near-zero relevance after this date.
tags
string[]
Optional string tags for filtering. Max 10 tags, 64 chars each.
meta
object
Arbitrary JSON metadata attached to the memory. Max 2KB.
Response
json
{"id":"mem_7xKzP3qR","workspace_id":"ws_abc123","text":"Client XYZ prefers async comms and morning meetings","importance":8,"tags":[],"temporal_type":"persistent","created_at":"2025-03-14T09:41:00Z","request_id":"req_Kx8mN7..."}
Deduplication
Before storing, the engine checks for semantic duplicates. If a memory with cosine similarity ≥ 0.97 already exists, the existing record is returned with status: "duplicate" and a duplicate_of field pointing to the original ID.
Filter to memories that have all of the specified tags.
include_decayed
boolean
Include expired temporal memories. Default false.
Scoring model
The composite score S is computed as a weighted sum:
formula
S =0.55 × similarity
+0.20 × recency
+0.15 × importance
+0.10 × frequency
× decay_multiplier
The decay_multiplier reduces scores for old low-importance memories and zeroes out expired temporal ones. High-importance memories (≥9) decay very slowly over 1,000 days.
Returns a ready-to-inject context string from the top-k memories, with deduplication and token budgeting applied.
POST/v1/context/inject
Pass the result directly as the system or context field in your LLM call. BizXEngine handles ranking, window management, and deduplication — you just pass a token budget.