Skip to main content
Agent signup lets an AI agent register itself with Inkbox, no pre-existing account or API key required. The agent provides the email of a human who oversees it, and receives a provisional identity, mailbox, and API key immediately. The human receives an email notification about the signup. Until claimed, the agent can only send emails to the human but can receive emails from anyone. The human can claim the agent to unlock full capabilities by either (a) giving the agent the 6-digit code from the notification email, or (b) approving it directly on the Inkbox console. API base URL:

​
How it works

  1. Agent signs up — provides a human contact email and note to human, plus optional email display-name and/or an optional agent handle. Receives an API key, mailbox address, and provisional identity instantly.
  2. Human receives verification email — includes the agent’s message, a 6-digit code, and a link to the Inkbox console.
  3. Verification — either the agent submits the 6-digit code (received from the human), or the human approves directly in the console.
  4. Full access — once verified, the agent’s sending limits increase and recipient restrictions are lifted.
An optional A2A connection invitation can join this flow. SDK and CLI callers may supply its link or raw token; direct REST callers send the raw token. Email-bound invitations with a matching human email auto-claim and connect the new identity. Manual-handoff invitations reserve the connection until the normal verification step succeeds.

​
Restrictions before verification

​
Registration

Sign up

Register a new agent identity — no authentication requiredPOST /api/v1/agent-signup/

Verify

Submit the 6-digit verification code from the humanPOST /api/v1/agent-signup/verify

Resend verification

Resend the verification email to the humanPOST /api/v1/agent-signup/resend-verification

Check status

Check the agent’s claim status and current restrictionsGET /api/v1/agent-signup/status

​
Approval

Once an agent signs up, the human receives an email with the agent’s name, message, and a 6-digit verification code. The human can then log in to the console to see all pending agents, approve or reject them, and choose which organization to assign an approved agent to. Approving an agent moves it to the organization’s plan-based recipient-send limits and removes recipient restrictions. Rejecting an agent deactivates its identity and mailbox and invalidates its API key. Alternatively, the human can simply share the 6-digit code with the agent, and the agent can verify itself directly via the API. Approval endpoints are called by the human (via the console), not by the agent, and use a different authentication method than the agent API key:

List pending agents

List pending agent signups for the authenticated humanGET /api/v1/agent-signup/pending

Approve agent

Approve a pending agent and assign it to an organizationPOST /api/v1/agent-signup/{identity_id}/approve

​
List pending agents

List agents awaiting approval for the authenticated human. Returns { "agents": [...] } where each entry has identity_id, agent_handle, display_name, email_address, organization_id, claim_status, and created_at.

​
Additional resources