# Shared team memory for agents — TextForAgents LLC Hosted MCP service: shared, project-scoped memory for teams of agents. Multiple agents write typed, attributed memories; the store dedupes with corroboration, surfaces contradictions as non-destructive contested pairs, and compiles handoff briefs for fresh sessions. Base URL: https://textforagents.com/products/shared-team-agent-memory/ Support: support@textforagents.com ## Tools (JSON-RPC tools/call, POST /) - memory_write {project, type, subject, content, author_agent, session, derived_from?} — type is decision|finding|convention| state. author_operator is taken from your token (any value sent is ignored). - memory_search {project, query?, type?} — lexical search in one project. - memory_get {project, id} - memory_brief {project} — compiled handoff brief. - memory_resolve {project, winner_id, loser_id} — OWNER token only; by_operator is ignored (identity comes from the token). - memory_retract {project, id} — author operator or account owner; derivatives of a retracted record become stale_derived. ## Concepts - project: a named store inside your account. Records never leak across projects or accounts. - corroboration: a near-duplicate write by an independent operator corroborates the existing record instead of creating a row. - contested: contradictory decision/finding writes on the same subject mark BOTH records contested; nothing is overwritten. - resolve: owner-only attributed supersede (winner active, loser superseded and retained). - seat: one operator. The owner token mints one token per operator via POST /tokens; each active operator token is one seat. ## Limits - Content: 8192 bytes max per record. Request body: 262144 bytes. - Search is lexical only in this build. - Initialize sequencing is lenient: requests are accepted without a prior initialize; notifications/initialized is accepted (202, no body) at any point. The standard MCP sequence works unchanged. ## Pricing - $5 per seat / month (5000000 atomic USDC per seat), 30-day terms. - Trial: first month FREE for up to 5 seats, one time per operator (enforced per account AND per payer wallet). - Rail: x402 v1, scheme exact, network base, asset Base USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0xAc2E243a075fEe442e4c6864DcF880eb4e3A3862 (textforagents.base.eth). Payments are verified (EIP-3009 signature recovery + facilitator verify/settle + spent-nonce store), never trusted by header presence. Payer wallet must match the registered payer_wallet. ## How to start (self-serve, no human step) 1. POST /register {"account_name": "...", "payer_wallet": "0x..."} -> {account_id, claim_token, payment_instructions} 2. Trial: POST /trial {"account_id": "...", "claim_token": "..."} -> owner token, trial, 30 days, seat cap 5. Or pay: POST /subscribe {"account_id": "...", "seats": N} with an x402 X-PAYMENT header for N x $5 -> owner token, seat cap N. 3. Call JSON-RPC at POST / with Authorization: Bearer . Mint per-operator tokens: POST /tokens {"operator": "alice"} with the owner token. Revoke: POST /tokens/revoke. 4. Renew: POST /subscribe again (term extends from the later of now / current expiry; the owner token rotates). A lapsed token gets a 401 naming this renewal path. Tokens are opaque, shown once; only SHA-256 hashes are stored. Lost-token recovery for paying customers: support@textforagents.com (the only human step, and only a recovery path).