Loading…
CONNECTED INTELLIGENCE text
Loading…
Authentication

Portal Access KeyOne key. Every tool.

Your Portal Access Key authenticates every request your AI tool makes to PF Create. One key per account — shared across all your AI tools and agents.

Getting your key

Get, rotate, or replace your key

1

Sign in at user.pfcreate.ca and open the Security section from the left menu.
Rotating generates a new key and immediately invalidates the old one. Any AI tool still using the old key will stop working until you update its configuration. Do this immediately if you think your key has been exposed.
Your key is displayed only once. Copy it now and store it in a password manager. If you close this screen without copying, rotate again to get a new one.
Paste the key into the MCP server URL header or configuration file for each AI tool you use — Claude Desktop, Cursor, n8n, etc. See the connection guides for your specific client.
If the key was exposed in a git repository, remove it and force-push. Check your git history too — the key may still be visible in previous commits. Use git-filter-repo to scrub it completely.
If you rotated because of a suspected compromise, check your account usage for any unexpected requests. Contact [email protected] if you see activity you don’t recognise.

All done!

Multiple tools & agents

One key, all your AI tools

PF Create uses one key per account. You don’t need a separate key for each AI tool — Claude.ai, Claude Desktop, Cursor, n8n, and any other clients you connect all use the same key.

This also means multiple AI agents running simultaneously under your account — for example, Claude Desktop and an n8n automation running in parallel — both authenticate with the same key. Requests from all agents count toward your account’s usage and rate limits.

If you’re on a Group or Enterprise plan, each team member has their own key. Usage and rate limits are tracked per key.

Works across all clientsClaude.ai, Claude Desktop, Claude Code, Cursor, n8n — all use the same key simultaneously.
Supports parallel agentsMultiple automations or agents running in parallel all authenticate with the same key.
One rotation updates everythingRotate once and update all your clients. There’s only one key to manage.
Security

Keeping your key secure

Treat your Portal Access Key like a password. Anyone with your key can make requests to PF Create as your account, consuming your usage and accessing your stored files and memory.

Store in a password managerStore your key in 1Password, Bitwarden, or similar. Never in a plain text file, Notion doc, or shared spreadsheet.
Never commit to version controlWhen setting up AI tools, paste the key directly into the config field. Don’t hardcode it into scripts or commit it to a git repository.
Don’t share your keyDon’t share your key with other people. Group plan members each have their own key. Sharing a key makes it impossible to audit who is doing what.
Rotate immediately if compromisedIf you think your key has been exposed — in a public repo, a screenshot, a log file — rotate it immediately. The old key stops working the moment you rotate.

Ready to connect?

Choose your AI tool and follow the step-by-step connection guide.