Install Jentic One Beta

Connect the Powered By Text API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Powered By Text API, 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%2Fpoweredbytext.com%2Fpoweredbytext" | 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%2Fpoweredbytext.com%2Fpoweredbytext" | 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.

Capabilities

What an agent can do with Powered By Text API.

Organize multi-campus communication structures with hierarchical organizational units

Create and manage subscriber groups within each campus for targeted messaging

Configure keyword-based opt-in flows for subscriber self-enrollment via text

Build and maintain reusable message templates with variable content

Retrieve account-level settings and configuration details

GET STARTED

Start building with Powered By Text API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Powered By Text API for, with concrete tasks.

★ Multi-Campus Communication Setup

Configure communication infrastructure for churches and nonprofits with multiple locations. The API enables creating organizational units (campuses) under a parent account, each with their own groups, keywords, and templates. This hierarchical structure allows location-specific messaging while maintaining centralized template management and account-level oversight across all campuses.

Create a new campus organizational unit named 'Downtown Campus' via POST /orgunit, then create a subscriber group named 'Youth Ministry' under it

Keyword-Based Subscriber Management

Set up keyword-based opt-in flows where congregation members text a keyword to subscribe to specific groups. The API manages keywords linked to groups under organizational units, enabling self-service enrollment. Members text a keyword (e.g., 'YOUTH') to a short code and are automatically added to the corresponding group for future messages.

List all keywords for the 'Youth Ministry' group using GET /orgunit/{orgunitId}/groups/{groupId}/keywords and verify the expected opt-in keyword is configured

Message Template Management

Create and maintain reusable message templates for recurring communications like event reminders, prayer requests, and announcements. Templates are managed at the account level and can be used across all campuses and groups. The API supports creating, listing, updating, and deleting templates, enabling centralized content management for consistent messaging.

Create a new message template named 'Sunday Service Reminder' with body 'Join us this Sunday at {time}. See you there!' using POST /accounts/{accountId}/templates

AI Agent Church Communication Management

Enable AI agents to manage church and nonprofit messaging infrastructure through Jentic. Agents discover group, keyword, and template management operations via intent search and receive operation schemas for constructing valid requests. Jentic handles OAuth 2.0 token acquisition automatically, enabling agents to focus on communication structure rather than authentication flows.

Search Jentic for 'create a subscriber group for church messaging', load the Powered By Text group creation schema, and execute to add a new ministry group under a campus

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for powered by text api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/accounts/{accountId}

Get account details

POST

/orgunit

Create a new campus organizational unit

GET

/orgunit/{orgunitId}/groups

List groups within a campus

POST

/orgunit/{orgunitId}/groups

Create a new subscriber group

GET

/orgunit/{orgunitId}/groups/{groupId}/keywords

List keywords for a group

GET

/accounts/{accountId}/templates

List message templates

POST

/accounts/{accountId}/templates

Create a new message template

GET

/accounts/{accountId}

Get account details

POST

/orgunit

Create a new campus organizational unit

GET

/orgunit/{orgunitId}/groups

List groups within a campus

POST

/orgunit/{orgunitId}/groups

Create a new subscriber group

GET

/orgunit/{orgunitId}/groups/{groupId}/keywords

List keywords for a group

GET

/accounts/{accountId}/templates

List message templates

POST

/accounts/{accountId}/templates

Create a new message template

Why Jentic?

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

Setup

Wiring the Powered By Text API by hand means running the OAuth 2.0 client-credentials exchange against login.poweredbytext.com, refreshing tokens, and choosing between the production and sandbox hosts yourself. Through Jentic you install once, import the Powered By Text API from the API Directory, store the client id and secret once, and your agent calls it.

Permission scoping

Powered By Text puts the org-unit and account ids in the URL path (/orgunit/{orgunitId}/..., /accounts/{accountId}/...), so a rule can pin your agent to one org unit: it can read that unit's groups, keywords, and templates and nothing else. You choose the operations it may call, so creating org units or templates is not included unless you add it.

Credential isolation

Your Powered By Text client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list messaging groups for an org unit' or 'create a message template', and Jentic returns the matching Powered By Text operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Powered By Text API through Jentic.

Why is there no official OpenAPI spec for Powered By Text API?

Powered By Text does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Powered By Text API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Powered By Text API use?

The Powered By Text API uses OAuth 2.0 with the Client Credentials flow. You obtain tokens from https://login.poweredbytext.com/connect/token using your client_id and client_secret. Through Jentic, OAuth token acquisition and refresh are handled automatically by the credential vault.

Can I manage multiple campuses with the Powered By Text API?

Yes. The /orgunit endpoint supports creating multiple organizational units (campuses) under a single account. Each campus can have its own groups, keywords, and messaging structure. Use POST /orgunit to create campuses and PUT /orgunit/{orgunitId} to update existing ones.

What are the rate limits for the Powered By Text API?

Rate limits depend on your account tier with Powered By Text. The API provides both production (api.poweredbytext.com) and sandbox (api-qa.poweredbytext.com) environments. Use the sandbox for development and testing to avoid impacting production rate allowances.

How do I create a subscriber group through the Powered By Text API using Jentic?

Install the SDK with pip install jentic, then search for 'create a messaging group for church'. Jentic returns the POST /orgunit/{orgunitId}/groups operation schema with the required orgunitId path parameter and group name/description body fields. Execute to create the group under a specific campus.

Does the Powered By Text API support message sending directly?

The documented API focuses on organizational structure management (accounts, campuses, groups, keywords, templates) rather than direct message dispatch. Message sending is typically handled through the platform's keyword-triggered and scheduled messaging features configured via groups and templates.

Can I limit what my agent is allowed to do with the Powered By Text API?

Yes. Because Jentic One is self-hosted, your own rules decide which Powered By Text operations and credentials the agent may use. Since org-unit and account ids sit in the URL path (/orgunit/{orgunitId}/..., /accounts/{accountId}/...), you can pin the agent to a single campus so it only reads that unit's groups, keywords, and templates. You choose the operations it can call, so write actions like POST /orgunit or POST /accounts/{accountId}/templates stay off unless you explicitly grant them.

Powered By Text API

AI ReadinessAI-Aware (A-)73/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticCommunicationsSms Messagingoauth213 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage church and nonprofit SMS communication structures including campuses, subscriber groups, opt-in keywords, and message templates. Supports multi-campus organizational hierarchies.

Use for: I need to create a new campus in my church messaging system, I want to set up a subscriber group for a ministry team, List all keywords configured for a specific group, Retrieve the message templates available for my account

Not supported: Does not handle direct SMS message dispatch, subscriber phone number validation, or billing management - use for organizational structure and template configuration only.

Jentic publishes the only available OpenAPI specification for Powered By Text API, keeping it validated and agent-ready. The Powered By Text API (also known as Ministry By Text) is a church and nonprofit messaging platform that provides management of accounts, organizational units (campuses), groups, keywords, and message templates. It enables multi-campus organizations to structure their SMS communication with keyword-based subscriber opt-in and reusable message templates across 13 endpoints using OAuth 2.0 client credentials authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Powered By Text API to your agent

Capabilities

Start building with Powered By Text API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Powered By Text API

Jentic AI Readiness Score

Powered By Text API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness