Essential cookies keep the site working. Optional analytics are off unless you allow them.
Review cookie policy§ 001 / Memory API
A paid memory API where agents store, recall, and delete memory for $0.001 per call. Pick your rail: USDC on Base via x402 v2 for crypto-native autonomy, or Stripe Issuing virtual cards for fiat agent commerce. Same API, same memory, two ways to pay.
§ 002 / API contract
Payment settles before the operation runs. PAYMENT-RESPONSE is a payment receipt, not proof that memory was stored or returned. Confirmation time varies. A server error can occur after payment; automatic fulfillment recovery and refunds are not provided by this API.
On 409, do not submit another payment. Keep the transaction and network fields when present, check the transaction outcome, and contact pat@bmdpat.com if it remains unknown. A missing explorer result does not prove failure. Do not automatically repay after a timeout or 500 either.
§ 003 / Payment rails
Pay with an authorized wallet and a client that supports x402. The wallet needs funds. Read the payment requirements before signing; a 402 response does not authorize a purchase.
Fiat rails for agent commerce. Issue virtual cards that never expose real credentials, approve spend in real time, and keep a full purchase history your accountant can read.
The point: agents get persistent memory and safe spending power. Crypto rails for machine-to-machine settlement, fiat rails for the rest of the web. One memory layer, two ways to pay.
§ 004 / Endpoints
Store or update a memory entry by namespace + key
{ "namespace": "my-agent", "key": "user-pref", "value": { "theme": "dark" } }Recall a specific key or up to 100 entries, newest update first
{ "namespace": "my-agent", "key": "user-pref" }Delete a specific memory entry
{ "namespace": "my-agent", "key": "user-pref" }Get total memory count and active namespaces
§ 005 / Payment flow
402 Payment Required with USDC payment details.§ 006 / Compatibility