Point your agent at Veezee

Just start: three interfaces, same tools, same credits, no signup. Call the vz CLI, MCP, or REST with no key and you get back a KEY_REQUIRED error carrying the exact fix: one free call mints a key, no card, no human. That key runs under a free budget of 200 credits per IP per day.

CLI#

npm install -g @veezee/sdk
vz init
vz linkedin profile get williamhgates
vz reddit search "notion alternative" --type comments
vz x profile nasa

vz init mints a free key and saves it to ~/.veezee/config, or set VEEZEE_API_KEY yourself (or pass --key). All commands: /docs/cli. The same package is a typed TypeScript SDK: /docs/sdk.

MCP#

https://mcp.veezee.io/linkedin

transport: streamable-http. Per-platform mounts: /linkedin, /reddit, /x, or https://mcp.veezee.io/all for every platform at once. Mint a key with POST https://api.veezee.io/v1/keys/mint and add Authorization: Bearer <api_key> to the client's connection headers. Exact snippets for Claude Code, Cursor, and other clients: /docs/clients.

REST#

curl -s -X POST https://api.veezee.io/v1/keys/mint | jq -r .key
curl "https://api.veezee.io/v1/linkedin/companies?identifier=microsoft" -H "Authorization: Bearer $VEEZEE_API_KEY"

Authorization: Bearer <api_key> on every call, plus an Idempotency-Key header on metered routes. Contract: /openapi.json, tool reference: /docs.

Let the agent set itself up#

Paste /agent-setup/prompt.md into any agent: it walks the whole path from the first KEY_REQUIRED response to authenticated use.

When you're ready to pay, buy a key at /upgrade: checkout credits the same key, nothing to reconfigure, and everything you already built keeps working. Lost keys are recovered at /recover.