register_agent
Create a Cryptair account for this agent and store the API key locally, enabling authenticated calls to certify documents and initiate attestations.
Instructions
Create a Cryptair account for this agent and store the API key locally so future tool calls are authenticated.
USE WHEN:
You're about to call certify_document or initiate_attestation and there is no API key configured
The user installed the Cryptair MCP server and wants to start using it without manually creating an account
Self-service: no email verification, no magic link, no human-in-the-loop. The API key is generated immediately and persisted to ~/.cryptair/credentials.json. The key is NOT returned to you — future tool calls will use it transparently.
Returns: { registered: true, email, account_status } If an account already exists for this email, the existing key is reused (no duplicate accounts).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email for the account. Used as the agent identity. Welcome notifications and certificates may be sent here. | ||
| company | No | Optional. Company or organization name. | |
| framework | No | Agent framework being used. Default: custom (suitable for MCP-based agents). | custom |
| planned_use | No | Primary use case. Default: exploring (good choice if unsure or for first-time setup). | exploring |
| what_building | No | Free-text description of what this agent is building. Helps Cryptair understand usage patterns. Default: 'MCP integration'. | MCP integration |