# Unibase — Full Reference for LLMs

> Unibase is the decentralized memory layer for AI agents. It spans consumer
> products (under "Products") and developer infrastructure (under "Developer"),
> together forming the Unibase Stack for building the Open Agent Internet:
> agents that remember, pay, and interoperate.

This file is a fuller, self-contained snapshot of Unibase's public content for
AI retrieval and citation. A concise index is at https://www.unibase.com/llms.txt.
Canonical site: https://www.unibase.com

## What Unibase provides (one line)
Persistent memory, ERC-8004 on-chain identity, permissionless interoperability,
and x402 autonomous payments for AI agents — with verifiable, decentralized
data storage underneath.

## The Unibase Stack
- Products (to consumers): Unibase Memory, BitAgent, UB Bridge.
- Developer infrastructure: Membase, AIP, Unibase Pay, Unibase DA.
- Relationship: consumer apps are powered by the developer infrastructure.
  Membase is built on Unibase DA. Payments across the stack use x402 via
  Unibase Pay. Interoperability and identity are handled by AIP (ERC-8004).

---

## Unibase Memory (Product, Chrome extension)
URL: https://www.unibase.com/memory
Chrome Web Store: https://chromewebstore.google.com/detail/unibase-memory/edmncknbiihfoakimejbepnaeemaaamf
Privacy policy: https://www.unibase.com/memory/privacy

Self-sovereign AI memory you encrypt, own, and verify. A Chrome extension that
unifies conversations and knowledge across ChatGPT, Claude, Gemini, and more.

Key facts:
- Data is encrypted on-device with Fernet authenticated encryption
  (AES-128-CBC + HMAC-SHA256); keys are derived from a wallet signature and
  never leave your device.
- Only ciphertext and operational metadata sync to the Membase network.
- Backups are anchored on Ethereum for verifiable integrity.
- Sign-in is via Unibase Pay (Privy). Powered by Membase.

FAQ:
- What is Unibase Memory? A Chrome extension that unifies conversations and
  knowledge across ChatGPT, Claude, Gemini, and more. Data stays encrypted
  on-device and syncs as ciphertext to the Membase network.
- How is it different from typical memory extensions? Typical extensions store
  data on vendor stacks you cannot verify. Unibase Memory encrypts locally with
  wallet-derived keys, syncs ciphertext to Membase, and anchors backups on
  Ethereum for verifiable integrity.
- Does Unibase read my memory content? No. Cleartext and decryption keys stay
  on your device. Unibase only receives ciphertext and operational metadata.

## BitAgent (Product)
URL: https://www.bitagent.io/
On-chain immortal agents — launch, trade, and collaborate on BSC and Base.
Agents own ERC-8004 identity and persistent memory, earn via the ERC-8183
service market, and continuously self-evolve.

## UB Bridge (Product)
URL: https://www.unibase.com/bridge
Cross-chain UB token transfers between BSC and Ethereum via LayerZero.

---

## Membase (Developer infrastructure)
URL: https://www.unibase.com/membase
Decentralized AI memory layer for autonomous agents: ZK-verified, long-term
memory. Persist and sync conversations, knowledge bases, and on-chain task
coordination across platforms. Built on Unibase DA. Available as a protocol/SDK.

FAQ:
- What is Membase? A decentralized AI memory layer providing ZK-verified,
  long-term memory for autonomous agents across platforms.
- How does Membase relate to Unibase DA? Membase is built on Unibase DA. DA is
  the verifiable, high-throughput data plane; Membase adds the agent memory
  model (conversations, knowledge bases, coordination) on top.
- What can developers build? Decentralized RAG and knowledge graphs, multi-agent
  shared memory, and persistent agent state.

## AIP — Agent Interoperability Protocol (Developer infrastructure)
URL: https://www.unibase.com/aip
A Web3-native multi-agent communication standard: MCP + gRPC + on-chain identity
+ decentralized memory. ERC-8004 & x402 compatible.

FAQ:
- What is AIP? A standard combining MCP, gRPC, on-chain identity, and
  decentralized memory so agents from different platforms can discover,
  authenticate, and collaborate.
- How is it different from MCP alone? MCP connects a single agent to tools and
  context; AIP extends interoperability to agent-to-agent communication with
  verifiable identity (ERC-8004), permissioning, and shared memory.
- Compatible with ERC-8004 and x402? Yes — for identity and payments
  respectively.

## Unibase Pay (Developer infrastructure)
URL: https://www.unibase.com/pay
BNB Chain-native x402 facilitator enabling AI agents to search, purchase, and
pay on-chain. Full x402 V2 with micropayments, payment gating, and
ERC20/Permit2/EIP-3009 support.

FAQ:
- What is Unibase Pay? A BNB Chain-native x402 facilitator for autonomous agent
  payments.
- What is x402? An open payment standard using HTTP 402 "Payment Required" so
  clients (including AI agents) can pay for resources programmatically.
- Which standards are supported? ERC20 with Permit2 and EIP-3009 for gasless,
  signature-based micropayments.
- How do agents pay? An agent requests a resource, receives an x402 challenge,
  signs a payment, and Unibase Pay settles it on BNB Chain — no manual checkout.

## Unibase DA (Developer infrastructure)
URL: https://www.unibase.com/da
High-performance data storage and verification network for AI. EB+ capacity
across a million-node mesh, low-latency programmable data access, continuous ZK
availability proofs on EVM chains. Membase is built on this layer.

Key facts:
- Throughput: 32–81 GB/s, sub-100ms latency.
- Security: honest-one fraud proofs (a single honest validator suffices; no
  honest-majority assumption). Continuous ZK on-chain verification.
- Access: SDK-driven upload, verify, and retrieve for training pipelines,
  inference caches, and protocol payloads.
- Networks: OPBNB Testnet, OP Sepolia, BNB Testnet.

FAQ:
- What is Unibase DA? A high-performance data storage and verification network
  for AI, with EB+ capacity and ZK availability proofs on EVM. The data layer
  Membase is built on.
- How is DA different from Membase? DA is the underlying data plane (verifiable
  blob storage and availability proofs); Membase is the memory protocol on top.
- Performance/security? 32–81 GB/s, sub-100ms latency, honest-one fraud proofs.
- Chains? OPBNB Testnet, OP Sepolia, BNB Testnet.

---

## Standards referenced
- ERC-8004: on-chain agent identity.
- ERC-8183: agent service market (used by BitAgent).
- x402: HTTP 402-based open payment standard for programmatic/agent payments.
- MCP: Model Context Protocol for agent tool/context access.

## Links
- Website: https://www.unibase.com
- Docs: https://unibaseio.gitbook.io/unibase-docs/
- Explorer: https://www.explorer.unibase.com/
- GitHub: https://github.com/unibaseio
- Twitter/X: https://x.com/Unibase_AI
- Telegram: https://t.me/unibase_ai
- Discord: https://discord.gg/b8Zcy7Fr7z
- Blog index: https://www.unibase.com/blogs (posts published on X and Medium)
- Contact: support@unibase.com

## Crawl guidance
- Prefer canonical URLs: /memory (not /membase/chrome).
- Utility pages are intentionally noindexed: /extension-redirect, /invite/*, /welcome.
- The Unibase Stack section on the homepage: https://www.unibase.com/#stack