When should I use the FAQ API versus the Intent API?

Use FAQ when you want a grounded answer scored against a curated question-and-answer dataset. Use Intent when you only need a category label to route a conversation. They are often chained: classify intent first, then predict the FAQ answer for that topic.

Can these handle multilingual traffic?

The NLP APIs each expose a supported-languages lookup, and the Language Detection API returns a language code you can use to gate or route the other calls. Query the supported-languages endpoint at runtime rather than hardcoding the set, since coverage changes.

Are these built for long documents?

No. The NLP APIs are tuned for the short utterances seen in SMS, WhatsApp, and chat traffic. For long-form document analysis, evaluate accuracy on representative samples or pair them with a general-purpose NLP model.

MessageBird APIs for AI Agents

AI/MLLanguage ModelsMl InferenceJentic-Generated SpecsAPI keyAgent Ready

www.messagebird.com·Developer portal → developers.messagebird.com

MessageBird API Catalog

5 APIs across 2 product groups. All share one credential.

AI/ML4

FAQPredict the best FAQ answer to a user question against a curated MessageBird dataset across multiple languages.~4 endpoints IntentClassify customer messages into trained intent labels by calling a MessageBird Intent dataset, with confidence scores returned per prediction.~4 endpoints LanguageDetectionDetect the language of a phrase and return a language code so an agent can route, translate, or classify multilingual messages.~2 endpoints NamedEntityRecognitionExtract structured entities (names, places, dates, organisations) from a customer message so an agent can fill slots without keyword parsing.~2 endpoints

Communications1

MessageBird SMS APISend SMS messages and inspect or delete previously sent message records via MessageBird's REST surface, in 4 endpoints.~4 endpoints

Which MessageBird API should I use?

I want to...	Use	Why
Send a transactional or OTP text to a phone number	MessageBird SMS API	The SMS API is the only one here that delivers messages; the NLP APIs only analyze text.
Decide what an inbound message is asking for	Intent	Intent returns a trained label with a confidence score; NER returns entities and FAQ returns a canned answer, which answer different questions.
Extract specific values like dates, names, or places from a message	NamedEntityRecognition	NER returns typed entity slots; Intent only returns the overall label and does not surface individual values.
Answer a support question from a vetted knowledge set	FAQ	FAQ scores a question against a curated dataset; Intent routes by category rather than returning an answer.
Identify which language a phrase is written in before routing	LanguageDetection	Language Detection returns a language code with no training step; Intent and NER assume the locale is already chosen.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring these MessageBird APIs by hand means attaching your AccessKey to requests against several different hosts (rest, intent, faq, language-detection, and ner) and handling routing and retries per host. With Jentic you install once, add the APIs you need from the Jentic directory, store the AccessKey once, and your agent calls them.

Permission scoping

You choose which operations your agent may call across the five APIs, so your own rules can grant SMS sending and inbound-message analysis while leaving message deletion or dataset reads out of reach. Where a dataset id appears in the path, a rule can pin the agent to a single dataset.

Credential isolation

Your MessageBird AccessKey is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same key covers all five APIs.

FAQs

Specific to using MessageBird APIs through Jentic.

Which MessageBird APIs are covered here?

Five: the SMS API for sending and managing text messages, plus four short-text NLP APIs for intent classification, language detection, named entity recognition, and FAQ answer prediction. The SMS API handles delivery and the other four interpret inbound text.

Do these APIs share one set of credentials?

Yes. Every MessageBird API here authenticates with the same AccessKey in the Authorization header, so a single credential works across all five surfaces. You store that AccessKey once in your own Jentic One instance.

How do the messaging and text-understanding APIs work together?

The SMS API sends outbound messages, and the Intent, NER, Language Detection, and FAQ APIs read the meaning of the free text that comes back. A typical flow sends a notification, then detects language, classifies intent, extracts entities, and answers or routes the reply.

Why are all the specs Jentic-generated?

MessageBird does not publish OpenAPI specifications for these products. Jentic generates and maintains the specs so agents can call each API through structured tooling, and validates them against the live endpoints.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs5 in catalogue

Endpoints16 indexed

AuthAPI key — 1 credential for all 5 APIs

ProvenanceJentic-generated specs

An agent can send SMS messages and reconcile or delete the resulting records, then classify inbound message intent, detect the language of a phrase, extract structured entities, and match a question to a curated FAQ dataset. This lets one agent both dispatch outbound texts and interpret the free-text replies that come back.

MessageBird pairs a global SMS delivery API with a focused stack of short-text NLP building blocks (intent classification, language detection, named entity recognition, and FAQ answer prediction) that are tuned for the kind of utterances seen in SMS and chat. That combination lets a single vendor cover both sending a message and understanding the reply, rather than treating messaging and text analysis as separate integrations.

Use for: Sending and managing SMS messages, and classifying, detecting the language of, extracting entities from, or matching FAQ answers to short customer text

Not supported: voice calls, WhatsApp messaging, free-form text generation, dataset training, long-form documents, message translation

Credentials: All five APIs use the same MessageBird AccessKey passed in the Authorization header, so one credential covers the SMS, Intent, FAQ, Language Detection, and NER surfaces.

Install Jentic One Beta

Connect the MessageBird APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MessageBird APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmessagebird.com" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmessagebird.com" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Once connected, ask your agent something like: “send an SMS and classify the inbound reply with MessageBird”.

What AI Agents Can Do with MessageBird

Each workflow spans multiple MessageBird APIs. Jentic routes each operation to the right API automatically.

Detect, classify, and answer an inbound message

When a customer reply arrives, detect its language, classify what it is asking for, and match it to a vetted FAQ answer. Language Detection picks the locale, Intent returns the labelled category with a confidence score, and FAQ returns a grounded answer the agent can send back or escalate on low confidence.

Example prompt:

Call predict-language to get the locale, POST the phrase to the Intent predict operation, then call the FAQ predict-answer operation on the matching dataset and reply if confidence clears the threshold.

APIs used

LanguageDetection + Intent + FAQ

Slot-fill a booking from a text and confirm by SMS

Extract the date and location from an inbound booking request, act on the structured values, then send a confirmation SMS. NER turns the free text into typed entities and the SMS API dispatches the confirmation with the returned message ID stored for auditing.

Example prompt:

POST the message to predict-entities, use the returned date and location to complete the booking, then POST a confirmation to /messages and store the message ID.

APIs used

NamedEntityRecognition + MessageBird SMS API

Route an inbound SMS reply to the right workflow

For replies to outbound SMS campaigns, classify the intent of each reply and forward it to the correct queue or automated action. The SMS API surfaces the sent-message records for reconciliation and Intent labels the inbound reply so the next step is chosen without keyword matching.

Example prompt:

List sent messages with GET /messages to reconcile the thread, then POST the inbound reply to the Intent predict operation and branch on the returned label.

APIs used

MessageBird SMS API + Intent

MessageBird APIs for AI Agents

MessageBird API Catalog

AI/ML4

Communications1

Which MessageBird API should I use?

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

Connect the MessageBird APIs to your agent

What AI Agents Can Do with MessageBird

If you need a different AI/ML vendor