# Mem Protocol

**Canonical:** https://apis.io/providers/mem-protocol/  
**APIs profiled:** 0

Mem Protocol (mem.so) was a San Francisco based startup, founded in 2021, building tools for the social layer of web3 - a decentralized social-media protocol focused on user data sovereignty, portable social graphs, and verifiable on-chain identity. The company raised a ~$3.1M seed round in 2021 led by Andreessen Horowitz (a16z crypto), with participation from Balaji Srinivasan and Polychain's Olaf Carlson-Wee. As of this enrichment pass the project appears dormant/defunct - the official domain mem.so resolves only to a parking IP and times out, and the alternate domain memprotocol.xyz redirects to a GoDaddy for-sale page. No live website, developer portal, API documentation, GitHub organization, SDK packages, or public API surface could be found. This profile remains an identity-only company record; there is nothing to enrich beyond the historical facts below.

## Kin Score — 5.0 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 5.0).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Tags

Company, Web3, Decentralized Social, Social Graph, Blockchain, Identity, Defunct

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/mem-protocol/). Scores are computed from the provider's own public artifacts under a published rubric.