Amazon Lex Model Building V2

Name: Amazon Lex Model Building V2 API
Brand: Amazon Lex Model Building V2
Availability: InStock

★ Only Publicly Available SpecAI/MLLanguage Modelshmac71 EndpointsREST

For Agents

Author and version Amazon Lex chatbots end-to-end — create bots, configure intents and slots, train locales, manage custom vocabulary, and publish via aliases.

Quickstart

Get started with Amazon Lex Model Building V2 in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Amazon Lex V2 bot"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Lex Model Building V2 API.

Create and configure Amazon Lex V2 bots, including locales, intents, slots, slot types, and custom vocabulary entries

Build a bot locale to compile its NLU model and make it ready for runtime serving

Manage bot versions and aliases so a chat client can be pinned to a specific tested release

Import and export bot configurations as ZIP archives for source control or cross-account promotion

GET STARTED

Start building with Amazon Lex Model Building V2 API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Amazon Lex Model Building V2, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Lex Model Building V2, keeping it validated and agent-ready. Lex Model Building V2 is the authoring control plane for Amazon Lex conversational bots — it manages bots, bot versions, locales, intents, slot types, slots, custom vocabulary and aliases, and orchestrates the build, import, export and tagging of those resources. The 71 endpoints cover the full bot lifecycle from CreateBot through BuildBotLocale, intent and slot configuration, custom vocabulary upload, version pinning and alias-based deployment.

Use Cases

Patterns agents use Amazon Lex Model Building V2 API for, with concrete tasks.

★ Author and Version a Conversational Bot End-to-End

Conversational AI teams need to define bots in code rather than the console. Lex Model Building V2 exposes the full authoring lifecycle as API calls — CreateBot, CreateBotLocale, CreateIntent, CreateSlotType, CreateSlot, BuildBotLocale and CreateBotVersion — so an agent can scaffold an entire conversational flow, train it, and pin a runtime alias to a tested version, all without touching the AWS console.

Call POST /bots/ with a bot name and IAM role, then POST /bots/{botId}/botversions/{botVersion}/botlocales/ with localeId=en_US, then POST a BuildBotLocale request and poll until status=Built

Promote Bots Between Environments via Import and Export

Promoting a Lex bot from development to staging to production benefits from a deterministic artefact rather than re-running create calls. The V2 model API supports CreateExport and CreateImport flows that package an entire bot definition as a ZIP archive, including locales, intents, slot types and custom vocabulary, and unpack it into a different account or region with role-scoped IAM credentials.

Call CreateExport for a botId+botVersion, poll until ExportStatus=Completed, download the ZIP, and call CreateImport in the target region with the same archive

Bias NLU Recognition With Domain-Specific Vocabulary

Domain-specific terms (drug names, product SKUs, regional spellings) are commonly mis-transcribed by generic NLU. Lex V2 supports custom vocabulary entries scoped per bot locale. An agent can batch-create or batch-update these entries from a CSV catalogue, rebuild the locale, and publish a new version — improving slot recognition accuracy for vertical use cases without retraining the underlying model.

Call /bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/customvocabulary/DEFAULT/batchcreate with an array of phrases and weights, then trigger BuildBotLocale to apply

AI Agent Integration for Bot Authoring Pipelines

Through Jentic, an agent can drive the entire Lex V2 model-building flow — create bot, configure locales and intents, build, version and tag — by chaining intent searches against the catalogue. Jentic returns each step's input schema and brokers AWS credentials, so an LLM can stand up or modify a Lex bot from a single user instruction without scripting against boto3.

Resolve the intent 'create a Lex V2 bot' via Jentic search, load the CreateBot schema, and execute it with a bot name, role ARN, and idle session TTL

Key Endpoints

71 endpoints — jentic publishes the only available openapi specification for amazon lex model building v2, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/bots/

Create a new Lex V2 bot

POST

/bots/{botId}/botversions/{botVersion}/botlocales/

Create a locale on a bot version

POST

/bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/intents/

Create an intent in a bot locale

POST

/bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/customvocabulary/DEFAULT/batchcreate

Batch-create custom vocabulary items

POST

/bots/{botId}/botaliases/

Create a bot alias pointing at a version

POST

/imports/

Import a bot from a ZIP archive

POST

/exports/

Export a bot version as a ZIP archive

POST

/bots/

Create a new Lex V2 bot

POST

/bots/{botId}/botversions/{botVersion}/botlocales/

Create a locale on a bot version

POST

/bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/intents/

Create an intent in a bot locale

POST

/bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/customvocabulary/DEFAULT/batchcreate

Batch-create custom vocabulary items

POST

/bots/{botId}/botaliases/

Create a bot alias pointing at a version

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys live in the Jentic MAXsystem vault. Jentic signs Lex V2 model requests with SigV4 on the agent's behalf, so raw IAM credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a Lex bot intent') and Jentic returns the matching Lex Model Building V2 operation with its input schema, so the agent can call CreateIntent, BuildBotLocale or CreateBotAlias without browsing the AWS docs.

Time to first call

Direct Lex V2 model API integration: 3-5 days for IAM scoping, build polling, version/alias workflow and import/export plumbing. Through Jentic: under a day — search, load schemas, chain operations.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon Lex Model Building (V1)

The earlier Lex V1 model API has a flatter resource layout but is in maintenance mode

Choose V2 for new bots — multi-locale support and richer slot types. Use V1 only when extending an existing V1 bot that has not yet been migrated.

Complementary

Amazon Polly

Polly synthesises the spoken responses played back by Lex voice bots

Use alongside Lex V2 when an agent needs to render bot prompts as speech for IVR or voice-first deployments.

Complementary

Amazon Comprehend

Comprehend provides general-purpose entity, sentiment, and language analysis for free-form text

Use when intent detection is not enough — Comprehend can pre-classify free-form user input before routing it to a Lex bot.

Complementary

AWS Lambda

Lambda hosts the fulfilment functions that a Lex bot invokes when an intent completes

Use to run the business logic behind an intent — e.g., booking a flight, looking up an order — without standing up a server.

FAQs

Specific to using Amazon Lex Model Building V2 API through Jentic.

Why is there no official OpenAPI spec for Amazon Lex Model Building V2?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Lex Model Building V2 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon Lex V2 model API use?

The model-building API is signed with AWS Signature Version 4 using IAM access key/secret pairs. Through Jentic, those AWS credentials sit in the MAXsystem vault and are used to sign each request on the agent's behalf so raw keys never enter the agent's context.

Can I create a complete chatbot through the Lex V2 API?

Yes. The API exposes the full authoring stack — CreateBot, CreateBotLocale, CreateIntent, CreateSlotType, CreateSlot, BuildBotLocale, CreateBotVersion and CreateBotAlias — so an agent can scaffold a bot, train its NLU, and publish a runtime alias entirely through API calls.

What are the rate limits for the Lex V2 model API?

AWS applies per-account and per-region throttling to the Lex control plane. Build operations are particularly slow and concurrency-limited, so design pipelines to poll DescribeBotLocale until status=Built rather than retrying tightly.

How do I train a bot locale through Jentic?

Use the Jentic search query 'build a Lex bot locale', load the operation behind /bots/{botId}/botversions/{botVersion}/botlocales/{localeId}/, and execute it with your botId, botVersion and localeId. Then poll DescribeBotLocale via Jentic until botLocaleStatus=Built before publishing a version.

How do I move a bot from one AWS account to another?

Use the Lex V2 export/import flow. Call CreateExport on the source botVersion, poll until ExportStatus=Completed, download the resulting ZIP, then call CreateImport in the target account with the same archive and a target bot name.