lupin.Open console

Lupin / Phone

Phone numbers, SMS and voice for AI agents

Bring an agent’s identity to text messages and telephone conversations.

Build an agent workflow with phone

A support or operations agent may need to continue a conversation beyond email. Lupin exposes number inventory, SMS and call operations through the same workspace API, while keeping number ownership, permitted destinations and the actual provider outcome attached to each operation.

What the API supports

From setup to a verified outcome

  1. Check the workspace

    Read capabilities and phone status before requesting a number or a call. Number and country availability depends on the configured phone provider.

  2. Choose the operation

    Review the number, destination, recurring price or call duration. The calling application must hold the applicable permissions and authorization.

  3. Track the result

    Keep the original operation identity and inspect call or message status. A provider acknowledgement is not proof that a person answered or a message was delivered.

Availability and limits

Check your workspace for its current configuration, usage and limits. Compare the plans before creating paid resources.

Start with the API reference

The following read endpoint is part of this capability. Authenticate with the relevant workspace key and inspect the documented response and permission requirements.

GET /v0/phone/status

OpenAPI specification · Phone documentation · Agent registration

Common questions

Can I let an agent call any phone number immediately?

No. Calls are subject to configured numbers, destination permissions, voice profiles, plan allowances and spending controls.

Are phone charges included in every subscription?

Phone usage is priced separately from the standard email, app-action, browser and sandbox allowances. Check the current workspace billing terms before creating paid phone resources.