Docs

Everything to call Veezee's LinkedIn, Reddit, and X tools over MCP or REST.

Start here#

Platforms#

Surfaces#

Reference#

Getting started#

Fastest path: paste one line into your agent and let it set itself up.

Your agent's chat
Fetch https://veezee.io/agent-setup/prompt.md and follow the setup instructions.

Or do the same by hand:

1. Get a free key#

Terminal
curl -s -X POST https://api.veezee.io/v1/keys/mint

One call returns a key (shown once) plus ready-made setup snippets. No account, no card. The CLI does this for you (npx @veezee/sdk init) and stores the key in ~/.veezee/config.

2. Call the API#

Terminal
curl "https://api.veezee.io/v1/linkedin/profiles?identifier=williamhgates" \
  -H "Authorization: Bearer $VEEZEE_API_KEY"

The free key includes 200 credits per IP per day, recent data only. If you call without a key, the error response tells you exactly how to get one, so an agent recovers on its own in one round-trip.

3. Or connect over MCP#

MCP endpoint
https://mcp.veezee.io/linkedin

transport: streamable-http, same free budget as REST. Claude Code, claude.ai, and other clients that support the MCP authorization spec open a browser sign-in automatically (email code, no password, no card, no key to copy). Other clients: put the key from step 1 in your MCP client's connection headers.

4. Need more than the free budget? Buy credits#

Pick a pack at /upgrade and pay: checkout credits the same key, so nothing needs reconfiguring.

Send the key as Authorization: Bearer <api_key> on every REST call, or in your MCP client's connection headers. Paid calls also send an Idempotency-Key header (any unique string per call) so a retried call is never billed twice.

Default path: use MCP when your host supports it, the SDK otherwise, REST as the fallback; the CLI and skills are conveniences layered on top of those.

Platforms#

Tools#

More reference#