X-API-Key header.
Sign up
Request body
Request example
JSON
Response (201)
JSON
api_key is returned only in this response. Store it immediately, because it cannot be retrieved again.
The invitation field is null when signup does not use an invitation. If you
received an A2A connection invitation, include it during the initial signup; do
not sign up first and request a verification code. An email-bound invitation
whose recipient matches human_email returns status: "accepted", claims the
identity, connects it, and does not send a second email. A manual-handoff
invitation returns status: "awaiting_verification"; submit the normal
verification code before the invitation expires to complete the connection. See
Connection invitations.
When invitation-assisted signup returns a claimed identity, read message for
plugin setup commands tailored to the supplied harness. Use the API key from
that same signup response; do not create another identity.
Signup also provisions a tunnel with the same name as the agent handle. For this example, the public hostname is sales-agent.inkboxwire.com. Connect your tunnel to start receiving traffic.
Error responses
Code examples
Verify
agent_claimed and full sending capabilities are unlocked.
Request body
Request example
JSON
Response (200)
JSON
invitation field is normally null. If verification completes a reserved
A2A invitation, it instead contains status: "accepted", the accepting identity,
the peer handles, and accepted_at. Human verification may still succeed after
an invitation is declined, revoked, or expires; in that case no A2A connection
is created.
For a recognized plugin-backed harness, message contains the exact setup
sequence used by the Console Quickstart: install the plugin, export the API key
returned at signup, bootstrap the existing agent identity, unset the key, and
run the plugin’s doctor command. The bootstrap step starts the local gateway and
may return a requires_human action that the agent must show to its human before
resuming. Unknown or unsupported harness values receive generic guidance rather
than commands that may not apply.
Error responses
Code examples
Resend verification
Response (200)
JSON
Error responses
Code examples
Check status
Response (200)
JSON

