SDKs

Pozy does not publish any client libraries yet: there is no npm, PyPI or other package to install. The supported ways to use Pozy today are the REST API, called with any HTTP client, and the MCP server at https://mcp.pozy.ai/mcp for AI assistants.

#What to use today

#Call the API

The API is plain HTTPS and JSON. Send your key in the Authorization header:

curl https://api.pozy.ai/v1/accounts \
  -H "Authorization: Bearer $POZY_API_KEY"

const res = await fetch("https://api.pozy.ai/v1/accounts", {
  headers: { Authorization: `Bearer ${process.env.POZY_API_KEY}` },
});
const body = await res.json();
if (!res.ok) throw new Error(body.error);
for (const account of body.accounts) {
  console.log(account.platform, account.username, account._id);
}

import os
import requests

resp = requests.get(
    "https://api.pozy.ai/v1/accounts",
    headers={"Authorization": f"Bearer {os.environ['POZY_API_KEY']}"},
    timeout=30,
)
resp.raise_for_status()
for account in resp.json()["accounts"]:
    print(account["platform"], account.get("username"), account["_id"])

The Node examples use the fetch built into Node.js 18 and later, so they need nothing installed. The Python examples use requests.

With plain HTTP you take care of a few things yourself:

• Send Authorization: Bearer pz_live_... on every request. See Authentication.
• Read errors from the JSON body: error, type, code and sometimes param and details. See Errors.
• Back off on 429 using the Retry-After and X-RateLimit-Reset headers. See Rate limits.
• Send an Idempotency-Key on writes you might retry. See Idempotency.

Node.js has a small fetch wrapper that does all four, which you can copy into your project.

#Operation ids

Every endpoint has an operationId in the spec, such as createPost. It is the last part of each API reference URL, the method name most generated clients use, and the name the MCP server runs through call_tool.

#Keep keys on the server

Call Pozy from server-side code: backends, workers, scripts and serverless functions. Never ship a pz_live_ key to a browser or a mobile app, because anyone can read it there. For a user-facing app, call Pozy from your backend, or create a profile-scoped, read-only key for the narrowest job.

#Next steps