ManyLives Paid Memory Set

x402

ManyLives Paid Memory Set is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-10).

Stores a key-value pair in persistent cloud memory for AI agents, with optional TTL, billed per call via x402 micropayment

Price / call$0.002

Seller volume →—

Success—

StatusUnknown

How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

Output

Returns a JSON object confirming the write: the key that was stored, the number of bytes written, a boolean 'stored' flag, the count of keys currently used, the expiry timestamp, and the total keys allowed under the account.

Example use cases

Persist trading strategy notes

“Store my current trading notes under the key 'trading/strategy' with value '{"bias":"long","asset":"BTC","confidence":0.8}' in agent memory for 60 days so I can retrieve them next session.”

Cache intermediate agent workflow state

“Save the key 'workflow/step3' with value '{"status":"pending","items":["ETH","SOL"]}' in ManyLives memory with a 7-day TTL so my pipeline can pick up where it left off.”

Store cross-session user preferences

“Write my preferences as '{"theme":"dark","currency":"USD","alerts":true}' to the key 'user/prefs' in agent memory and keep it for 90 days.”

Technical details

Endpoint

POSThttps://api.manylives.me/paid/memory/set?utm_source=zero.xyz

When to prefer

Choose this endpoint when an AI agent needs lightweight, pay-per-call persistent key-value memory without setting up a database or account — especially useful in autonomous trading agent pipelines built on ManyLives where memory needs to survive across sessions. Prefer it over self-hosted or account-gated storage when cost needs to scale with actual usage via USDC micropayments on Base.

Side effects

Key exceeds 128 characters or contains invalid characters — returns validation error
Value exceeds 64 KB limit — returns payload too large error
ttl_days outside 1-365 range — returns validation error
Payment fails or insufficient USDC balance — returns 402 Payment Required
Keys quota exhausted (keys_used >= keys_allowed) — returns quota exceeded error
Missing required 'key' or 'value' fields — returns 400 Bad Request

Input

Schema · Request body

Field	Type	Description
key	string	1-128 characters: letters, digits, . _ - : / (required)
value	string	string or any JSON value (required, max 64 KB)
ttl_days	string	optional 1-365 (default 30)

Output

Schema · Response

{
  "type": "json",
  "example": {
    "key": "project/notes",
    "bytes": 42,
    "stored": true,
    "keys_used": 3,
    "expires_at": "2026-11-08T12:00:00Z",
    "keys_allowed": 200
  }
}

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"