Use API Keys when another system needs machine access to Farin.
The safest default is still the smallest key that can do the job.
Quick facts
Start here
- Least privilege is the right default for API keys.
- Old keys should be reviewed and revoked on a regular cadence.
- One key per integration is easier to manage than one shared key for everything.
Step 1: Create only the key the integration really needs
Open API Keys and create a new key only when the integration scope is clear.
Name the key clearly so the team knows which system owns it later.
- 1 Give the key a clear name so the team knows which integration owns it later.
- 2 Grant only the domains and access level the integration actually needs.
- 3 Review the existing key list during every audit so old or revoked access is obvious.
Step 2: Review and revoke old keys cleanly
- Retire keys that no longer belong to an active integration.
- Do not leave mystery keys active longer than necessary.
Share instructions with your agent
If you are setting up an AI agent (like Claude Code, Gemini CLI, or a custom assistant), you can share our Skill instructions to help it use the Farin API correctly.
- Open Farin MCP Skill for agents connecting via Model Context Protocol.
- Open Farin CLI Skill for agents with terminal access.