Overview

Overview

An agent can drive Graphon the same way your code does. Connect the agent to the Graphon MCP server, or let it call the HTTP API with an API key. In both cases, a role limits what the agent can do.

Connect over MCP

The Graphon MCP server gives an agent tools for workspaces, members, API keys, buckets, and objects, and for search, answers, and research over an indexed bucket or a dataset. Most clients sign in with OAuth, and you pick the role of the agent on the consent page. See Connect for the steps for Claude Code, claude.ai, ChatGPT, Codex, Cursor, and VS Code. Tools lists every tool and the role that it needs.

Mint an agent key

An agent that uses the HTTP API, or an MCP client that sends a header, needs an API key. Create a key with only the role that the agent needs. Give an agent that only reads a viewer key. Use editor only when the agent writes objects. A workspace API key keeps working when the person who made it leaves, so it suits a long-running agent.

# An agent that only reads
graphon api-keys create --name "research-agent" --owner workspace --role viewer

# An agent that also writes objects
graphon api-keys create --name "ingest-agent" --owner workspace --role editor

Call the HTTP API

The agent sends the key as a bearer token, exactly like the samples in the API reference. Each endpoint page has an Agent sample.

export GRAPHON_AGENT_KEY="gak_..."
export GRAPHON_WORKSPACE_ID="<workspace id>"

curl \
  --url "https://storage.beta.graphon.sh/v1/workspaces/$GRAPHON_WORKSPACE_ID/buckets" \
  --header "Authorization: Bearer $GRAPHON_AGENT_KEY"