Invite people
invite_usersInvite people into this Project by email, all into every Role named plus Member. With no Roles named, they hold Member. Ekaya Central previews seats first; invitations are sent only when that preview adds no billable seat: a new seat among the seats the plan includes changes no bill and is sent without confirmation. Central decides seats and charges at send time; a concurrent invitation can still make the send add a billable seat. If the preview adds billable seats, or states no charge figures, sends nothing and returns seat_purchase_requires_confirmation with the preview and human_link to Roles and Members. Give that link to the person so an Administrator can review and confirm the purchase. Each sent address is reported as invited, already_member or already_invited. An invited person holds those Roles from invitation onward. At most 50 addresses at a time. Administrators take no seat and need no Team upgrade or seat confirmation. Ekaya Solo includes one User; every further User requires Ekaya Team. Check list_users invitation_eligibility before preparing Roles or app access — a team_required result is reported unrestricted for Administrator invitations and never refuses them. Eligibility is checked again on every invitation.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"emails": "<emails>"
},
"name": "invite_users"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| emails | Yes | Email addresses to invite | |
| role_ids | No | UUIDs of the Roles every invited person will hold in addition to Member; omitted or empty means Member |