README

Created By
Mooksea year ago
Overview

what is MyLife?

MyLife is an AI-Agent platform designed to help users capture, shape, and share their cherished memories, wisdom, stories, ideas, and more. It represents a decentralized effort towards sustainability and security in memory management.

how to use MyLife?

To use MyLife, users can interact with the platform to retrieve public memories and access basic elements. The platform is currently in development, with plans to enhance user experiences by creating reliving memory experiences in the future.

key features of MyLife?

  • Decentralized memory storage for sustainability and security.
  • Ability to capture and share personal memories and stories.
  • Future enhancements for reliving memory experiences.

use cases of MyLife?

  1. Capturing personal stories and memories for future generations.
  2. Sharing wisdom and experiences with a community.
  3. Creating a digital archive of cherished moments.

FAQ from MyLife?

  • Can I retrieve private memories?

Currently, MyLife only allows retrieval of public memories.

  • Is MyLife free to use?

The platform is in development, and details about pricing will be available upon launch.

  • How secure is my data on MyLife?

MyLife is built on a decentralized framework aimed at ensuring the sustainability and security of user data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mookse
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

37 minutes ago