API keys

One key. Your agent already knows how to seal.

Create a key for each application or agent. Every key uses your account’s proofs: 1,000 a day, free.

Give this to your agent

Read https://sellat.app/skill.md and set up Sellat for me.

Your agent reads the Sellat skill, installs it in your client and asks you for the key. Files never leave your machine: only their SHA-256 fingerprint travels.

Connect your tool

Replace sellat_… with your key

Pick what you work with. In every case the file is hashed on your machine and Sellat receives only the hash.

One line in your terminal: the MCP server

claude mcp add sellat -e SELLAT_API_TOKEN=sellat_… -- npx -y sellat-mcp

.cursor/mcp.json or claude_desktop_config.json

{
  "mcpServers": {
    "sellat": {
      "command": "npx",
      "args": ["-y", "sellat-mcp"],
      "env": { "SELLAT_API_TOKEN": "sellat_…" }
    }
  }
}

The Agent Skill, for any client that supports them

npx skills add skanthemore/sellat-cli --skill sellat
export SELLAT_API_TOKEN=sellat_…

sellat-cli: one file’s proof, waiting for the anchor

export SELLAT_API_TOKEN=sellat_…
npx -y sellat-cli stamp ./contract.pdf --wait

Your first request: the file’s hash, never the file

curl https://sellat.app/api/v2/proofs \
  -H "Authorization: Bearer sellat_…" \
  -H "Content-Type: application/json" \
  -d '{"hash":"<sha256>","name":"contract.pdf"}'

One key. Your agent already knows how to seal.

Connect your tool

No key: pay per call

More