Back to Browse
SCRIPTMASTERLABS SqueezeOS Memory Graph Store
x402
SCRIPTMASTERLABS SqueezeOS Memory Graph Store is a paid API for AI agents from squeezeos-api.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-14).
Stores typed, tagged memory entries (episodic, semantic, procedural, or custom) into an agent-namespaced persistent memory graph with provenance confidence scoring.
Price / call$0.01
Success—
StatusUnknown
How this service works
SCRIPTMASTERLABS SqueezeOS: agent-native APIs, MCP discovery, verifiable x402 payments, market intelligence, and machine-commerce infrastructure. Truth First. Proof Always. Pay Only for Accepted Delivery.
Output
Returns a JSON confirmation that the memory was accepted and stored in the SML Memory Graph, including the product name and a note that route-specific live values are returned after successful accepted delivery.
Example use cases
Logging agent session context
“Save a semantic memory for agent 'market-analyst-01' with the content 'AAPL has consistently outperformed QQQ over trailing 12 months', tagged 'equities' and 'macro', with a confidence of 0.85.”
Recording user preference for personalization
“Store an episodic memory for agent 'assistant-alpha' that says 'User prefers concise bullet-point summaries over long paragraphs', with tags 'preferences' and 'communication-style', and provenance confidence 0.95.”
Persisting procedural workflow step
“Write a procedural memory to the SqueezeOS memory graph for agent 'workflow-bot-3' with content 'Always verify ticker symbol before placing equity lookup', tagged 'rules' and 'equities', confidence 0.8.”
Technical details
Endpoint
POSThttps://squeezeos-api.onrender.com/api/memory/store?utm_source=zero.xyzWhen to prefer
Choose this endpoint when an AI agent needs to persist typed, tagged memory entries to a namespaced, provenance-aware memory graph — particularly in multi-agent or long-running workflows where episodic, semantic, or procedural memory must survive across sessions. Prefer this over in-process state or generic key-value stores when you need memory typed by category, tagged for retrieval, and associated with a specific agent namespace with traceable confidence scoring.
Side effects
- Missing required 'content' field causes rejection
- Missing or invalid 'agent_id' causes namespace error
- Provenance object missing 'confidence' field fails schema validation
- Payment not accepted (x402 flow failure) results in no storage
- Invalid memory type value outside allowed enum may cause processing error
- Service unavailability on Render.com hosting leads to 5xx errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| tags | array | |
| type | string | episodic, semantic, procedural, or custom |
| content | string | Memory text |
| agent_id | string | Agent namespace |
| provenance | object |
Output
Schema · Response
{
"type": "json",
"example": {
"note": "Route-specific live values are returned after successful accepted delivery.",
"product": "SML Memory Graph Store"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"