🔬

Early preview: This API is in early preview. Fill out this form to request early access.

Hello! How can I help?

Agent

/chat

/image

/audio

/embeddings

ChatGPT

Claude

Why teams use the Models API

Platform teams adopt a single, unified API to standardize access, observe spend, and avoid bespoke integrations for every new model. The Models API brings that pattern to monday.com: your apps call familiar endpoints (/chat/completions, /embeddings, /images/generations, /audio/speech), while monday handles routing to upstream providers and reconciles usage against your workspace.

Another reason is compliance, legal, and governance. Instead of creating new business relationships, security reviews, and procurement cycles with each LLM vendor, you access models through your existing monday subscription and the vendor relationship your company has already approved with monday.com (IT, legal, procurement, and security). You get broad model coverage without multiplying third party agreements and onboarding steps.

Pricing and metering

During early preview, the Models API itself has no separate subscription fee. Usage is metered in monday AI tokens based on underlying provider cost, plus the rules below.

Monday chat aliases: For POST /chat/completions, when you pass one of our supported monday-* aliases (monday-fast, monday-standard, monday-powerful) so the Models API resolves to the mapped Claude models, we do not add any extra fee beyond underlying usage. See Supported models for the map.

All other model usage: We currently apply a surcharge on top of underlying usage when you either (a) call /chat/completions with a direct vendor model ID (for example claude-sonnet-4-6 instead of monday-standard), or (b) use any supported model on /embeddings, /images/generations, or /audio/speech (these endpoints do not use chat aliases).

See also