Gridz documentation

Gridz gives you a verifiable profile — a page and an identity you control with your wallet. Your name lives at you.gridz.eth on Base; your public page lives at you.gridz.bio. Every field is cryptographically signed, so anyone can prove it came from you.

For AI & agents

Machine-readable index: llms.txt, skill.md, and the For AI hub — APIs, MCP, CLI, verification, and guardrails.

Start here

What you get

  • ENS identityalias.gridz.eth, resolved on Base.
  • Public profile pagehttps://alias.gridz.bio with a shareable layout.
  • JSON APIGET /api/profile/alias.gridz.eth for apps, bots, and integrations.
  • Signed attestations — each field (name, bio, links, widgets) carries a proof your wallet signed it.
  • Widget gallery — stats, polls, countdowns, org token listings, and more in a Spritz-style bento grid.
  • Query & verify — every profile page links to API fetch and offline verification steps for that ENS name.

Who is this for?

  • People — a link-in-bio you actually own, not a platform account.
  • Organizations — list official token contracts by chain with the gridz.tokens widget.
  • Builders — embed profiles with @gridz/react, fetch via the API, or verify offline with @gridz/core.
  • AI agents — same Grid model and verification; optional 1Claw HSM signing via @gridz/oneclaw and @gridz/mcp.

Open toolkit

Gridz is an open framework — not just this website. The specs, TypeScript packages, Python packages, smart contracts, and CLI all live in the Gridz-Protocol org on GitHub (gridz, gridz-js, gridz-examples, …). See the Toolkit page for what each package does and when you'd use it.

Why Gridz

  • Verifiable, not trusted — the signature is the source of truth; websites and databases are just views of it.
  • Your keys, your profile — Gridz never holds your private key. You sign in the browser or with your own signer.
  • One model everywhere — humans, agents, and orgs use the same Grid format; TypeScript and Python agree byte-for-byte.