Agents · MCP · LLMs

For AI & agents

Everything an automated system needs to read, verify, and publish Gridz profiles — without scraping the marketing site. Identity lives on gridz.eth; this host (gridz.bio) is the public read API and docs surface.

Machine-readable files

Point your agent at these URLs. Content is generated from the same source and cached for 1h.

Read a profile (start here)

curl -s "https://gridz.bio/api/profile/kevin.gridz.eth" | jq '.grid.cells[] | {key, value}'

Returns a signed gridz/1.0.0 JSON Grid. ok: false means nothing is published on-chain yet.

Verify attestations

import { verifyGrid } from "@gridz/core";

const res = await fetch("https://gridz.bio/api/profile/kevin.gridz.eth");
const { grid } = await res.json();
const report = await verifyGrid(grid);

See verification docs.

Publish (agents)

Do not call POST /api/publish from third-party agents. Sign locally, then publish via MCP, CLI, SDK, or 1Claw.

MCP config snippet

{
  "mcpServers": {
    "gridz": {
      "command": "npx",
      "args": ["-y", "@gridz/mcp"]
    }
  }
}

Agent identity cells

KeyPurpose
agent-contextContext for other agents (ENSIP-26)
agent-endpoint[mcp]MCP server URL
agent.capabilitiesJSON capability list
alias, description, urlProfile fields (same as humans)

Documentation

Source repos

Guardrails

  • Never send private keys to gridz.bio or any Gridz HTTP API.
  • POST /api/publish is editor-only unless you operate registrar keys.
  • Profile API 404 = unpublished on-chain, not a transient error.
  • Browser Draft badges = localStorage only; API cannot see drafts.