PAT Tokens

Personal Access Tokens (PAT) let you authenticate with any iopho product without interactive OAuth. PATs are permanent until revoked — ideal for CI pipelines, long-running agents, and headless environments.

Token format

All iopho PATs use the rdk_ prefix:

rdk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Generate a token

Each product has its own token settings page:

Product	Token settings
Reedle	app.reedle.iopho.com → Settings → Integrations → CLI Token
PromptNote	app.promptnoteapp.com → Settings → API → Generate Token
Wribble	app.wribble.iopho.com → Settings → Integrations → CLI Token
Catto	app.catto.iopho.com → Settings → Integrations → CLI Token
Knotto	app.knotto.iopho.com → Settings → Integrations → CLI Token

Authenticate the CLI

Reedle

reedle auth token rdk_your_token_here

PromptNote

pnote auth token rdk_your_token_here

Wribble

wribble auth token rdk_your_token_here

Catto

catto auth token rdk_your_token_here

Configure MCP with PAT

Add to your MCP client config (e.g. ~/.claude/settings.json):

{
  "mcpServers": {
    "reedle": {
      "command": "npx",
      "args": ["-y", "reedle-cli", "mcp"],
      "env": {
        "REEDLE_TOKEN": "rdk_your_token_here"
      }
    }
  }
}

Caution

Store PATs in environment variables or a secrets manager — never commit them to source control.

Security

• PATs are stored as SHA-256 hashes in the database — the raw token is never stored
• Tokens are scoped to your account and obey all RLS policies
• Revoke tokens any time from the product settings page