composio-mnemopay
MnemoPay integration for Composio -- persistent memory, micropayments, and trust scoring for AI agents.
Installation
pip install composio-mnemopay
With Composio provider support:
pip install composio-mnemopay[composio]
Quick start
Standalone (no Composio dependency)
from composio_mnemopay import MnemoPayClient
client = MnemoPayClient(server_url="https://mnemopay-mcp.fly.dev")
# Store a memory
result = client.call_tool("remember", {"content": "User prefers dark mode"})
print(result.value)
# Recall memories
result = client.call_tool("recall", {"query": "preferences"})
print(result.value)
# Check balance
result = client.call_tool("balance", {})
print(result.value)
With Composio provider
from composio import Composio
from composio_mnemopay import MnemoPayProvider
composio = Composio(provider=MnemoPayProvider())
tools = composio.tools.get(user_id="default", toolkits=["mnemopay"])
Tools
| Category | Tool | Description |
|---|---|---|
| Memory | MNEMOPAY_REMEMBER |
Store a persistent memory |
| Memory | MNEMOPAY_RECALL |
Semantic search over memories |
| Memory | MNEMOPAY_FORGET |
Delete a memory by ID |
| Memory | MNEMOPAY_REINFORCE |
Boost a memory's importance |
| Memory | MNEMOPAY_CONSOLIDATE |
Prune stale memories |
| Payments | MNEMOPAY_CHARGE |
Create an escrow charge |
| Payments | MNEMOPAY_SETTLE |
Finalize a pending escrow |
| Payments | MNEMOPAY_REFUND |
Refund a transaction |
| Observability | MNEMOPAY_BALANCE |
Wallet balance + reputation |
| Observability | MNEMOPAY_PROFILE |
Full agent stats |
| Observability | MNEMOPAY_REPUTATION |
Detailed reputation report |
| Observability | MNEMOPAY_LOGS |
Immutable audit trail |
| Observability | MNEMOPAY_HISTORY |
Transaction history |
Environment variables
| Variable | Default | Description |
|---|---|---|
MNEMOPAY_SERVER_URL |
https://mnemopay-mcp.fly.dev |
MCP server endpoint |
MNEMOPAY_AGENT_ID |
composio-agent |
Agent identifier |
MNEMOPAY_MODE |
quick |
Server mode |
License
MIT
Metadata
Release files for composio-mnemopay 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| composio_mnemopay-0.1.0.tar.gz | 6.6 kB | Without provenance | Details for composio_mnemopay-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| composio_mnemopay-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for composio_mnemopay-0.1.0-py3-none-any.whl |
Total release size: 14.7 kB
Release files / composio_mnemopay-0.1.0.tar.gz
| Download URL | composio_mnemopay-0.1.0.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ec9ca80abeda5ed04df55e52a9e8e001de892f0ac037a17f9cb5f9d11211677
|
|
BLAKE2b-256 checksum How to use checksums |
feef1d664f1f94bfa8a42437ce36a9a17f21d2602d58ca322494531b522ed572
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / composio_mnemopay-0.1.0-py3-none-any.whl
| Download URL | composio_mnemopay-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2ffdc5ed85435ff9b49a2083343cd31e2eaf2db130f93e8454f656b0004cac9
|
|
BLAKE2b-256 checksum How to use checksums |
f86f1b65e40b9d81ba813695276551bdb2de06f00b7135fe1be267016357bba4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for composio-mnemopay 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.