Overview
The Agent Onboarding API lets AI agents (Claude, GPT, Cursor, etc.) create Ekso workspaces programmatically — the same outcome as a human filling out the sign-up form, but via a structured two-step API. No SaaS product has standardized agent-driven sign-up yet. Ekso is leading the way.How it works
Agent onboarding is a two-step flow with email verification to prevent abuse:Request verification code
The agent sends the user’s details (name, email, company, domain) to the code endpoint. Ekso validates the inputs and emails a 6-digit verification code to the user.
Endpoints
Step 1: Send verification code
Step 2: Verify code and create workspace
Validation rules
| Field | Rules |
|---|---|
name | Required, non-empty |
email | Required, valid email format |
company | Required, non-empty |
domain | Required, 3-20 characters, lowercase alphanumeric and hyphens |
Error codes
All errors return a structured response with a machine-readablecode field:
| HTTP Status | Code | Description |
|---|---|---|
| 409 | DOMAIN_TAKEN | The requested domain is already in use |
| 422 | DOMAIN_BLACKLISTED | The domain is reserved or blacklisted |
| 422 | DOMAIN_TOO_SHORT | Domain must be at least 3 characters |
| 422 | DOMAIN_TOO_LONG | Domain must be at most 20 characters |
| 422 | INVALID_VERIFICATION_CODE | The verification code is incorrect or already used |
| 422 | VERIFICATION_CODE_EXPIRED | The verification code has expired (codes are valid for 10 minutes) |
| 429 | — | Rate limit exceeded (5 requests per 5 minutes per IP) |
Rate limits
Both endpoints share a rate limit of 5 requests per 5 minutes per IP address. Additionally, verification codes cannot be re-requested for the same email within 2 minutes.Example agent conversation
Here’s how an AI agent might guide a user through workspace creation:Discovery
Agents can discover the onboarding API through:- llms.txt —
https://ekso.app/llms.txt - A2A Agent Card —
https://ekso.app/.well-known/agent-card.json - This documentation —
https://ekso.dev/guide/agent-onboarding