canonical: https://jentic.com/apis/textbetter.com/textbetter

# TextBetter API

TextBetter SMS API for sending and receiving text messages via landline numbers. Supports SMS and MMS with Base64-encoded image attachments. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send outgoing sms/mms messages. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Send outgoing SMS/MMS messages
- Manage communications data programmatically
- Integrate TextBetter API into automated workflows
- Query and filter TextBetter API records by parameters
- Monitor TextBetter API operational status and events

## Use cases

### Communications Operations

Use the TextBetter API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including send outgoing sms/mms messages.

Example prompt: Call POST /SendOutgoingMessages to send outgoing sms/mms messages

### Data Retrieval and Monitoring

Query TextBetter API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary TextBetter API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call TextBetter API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'send outgoing sms/mms messages', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/SendOutgoingMessages` | Send outgoing SMS/MMS messages |

## Key resources

- **Messages** — Operations related to Messages

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/textbetter.com/textbetter/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the TextBetter API by hand means learning its X-API-Key header auth against the api2.textbetter.com/api host and coding its outgoing-message call yourself. Through Jentic you install once, import the TextBetter API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** TextBetter carries the recipient and message in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending outgoing messages. You choose the operations it may call, so it runs only the endpoints you allow.
- **Credential handling:** Your TextBetter API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'send an outgoing SMS or MMS message', and Jentic returns the matching TextBetter API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the TextBetter API use?

The TextBetter API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I send outgoing sms/mms messages with the TextBetter API?

Yes. Use the POST /SendOutgoingMessages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TextBetter API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I send outgoing sms/mms messages through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send outgoing sms/mms messages'. Jentic returns the matching TextBetter API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TextBetter API have?

The TextBetter API exposes 1 endpoints covering messages operations.

### Can I limit what my agent is allowed to do with the TextBetter API?

Yes. Because you run Jentic One yourself, your own rules decide which TextBetter operations and credentials the agent may use. The TextBetter API exposes a single operation, POST /SendOutgoingMessages, which carries the recipient and message text in the request body, so you can allow just that call and withhold every other endpoint. Since the API key is held by your own instance and injected only when an approved operation runs, the agent can send outgoing SMS or MMS messages while staying inside the boundary you set.