Install Jentic One Beta

Connect the Text In Church API to your agent

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

Get account details

Create or update account metadata

Delete account metadata

Query and filter Text In Church API records by parameters

Monitor Text In Church API operational status and events

GET STARTED

Start building with Text In Church API

Explore with Jentic One

View OpenAPI Document

Automated Account Management

Automate account operations by combining multiple Text In Church API endpoints. Agents can create or update account metadata and then get account metadata in a single workflow.

Call POST /accountMeta.php to create or update account metadata, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Text In Church 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 bearer tokens manually.

Search Jentic for 'get account details', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

46 endpoints — text in church messaging and contact management api for church communications, including messaging, contacts, groups, calls, workflows, and connect cards.

METHOD

PATH

DESCRIPTION

GET

/account.php

Get account details

POST

/accountMeta.php

Create or update account metadata

GET

/accountMeta.php

Get account metadata

DELETE

/accountMeta.php

Delete account metadata

POST

/contact.php

Create or update a contact

GET

/contact.php

Get contacts

DELETE

/contact.php

Delete a contact

POST

/contactComment.php

Create a contact comment

GET

/account.php

Get account details

POST

/accountMeta.php

Create or update account metadata

GET

/accountMeta.php

Get account metadata

DELETE

/accountMeta.php

Delete account metadata

POST

/contact.php

Create or update a contact

GET

/contact.php

Get contacts

DELETE

/contact.php

Delete a contact

POST

/contactComment.php

Create a contact comment

Why Jentic?

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

Setup

Wiring Text In Church by hand means learning its bearer auth against api.textinchurch.com and threading the token through every contact and account request yourself. Through Jentic you install once, import Text In Church from the API Directory, store the token once, and your agent calls it.

Permission scoping

Text In Church addresses contacts and account records through operations on endpoints like /contact.php and /accountMeta.php, so limit the agent to the operations it needs, such as reading account details or adding a contact. You choose that set, so destructive operations like deleting a contact are not included unless you add them.

Credential isolation

Your Text In Church token 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.

Intent-based discovery

Agents search Jentic by intent such as 'get account details' or 'add a contact', and Jentic returns the matching Text In Church operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Text In Church API through Jentic.

What authentication does the Text In Church API use?

The Text In Church API uses a Bearer token in the Authorization 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 get account details with the Text In Church API?

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

What are the rate limits for the Text In Church 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 get account details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account details'. Jentic returns the matching Text In Church API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Text In Church API have?

The Text In Church API exposes 46 endpoints covering account, contacts, messages operations.

Can I limit what my agent is allowed to do with the Text In Church API?

Yes. Because you run Jentic One yourself, you decide which Text In Church operations your agent can call, and your own rules govern which credentials it uses. You can allow read-only calls such as getting account details from GET /account.php or reading contacts, while withholding writes to /accountMeta.php or /contact.php. Destructive operations like deleting a contact stay off limits unless you explicitly add them to the agent's allowed set.

Text In Church API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer46 EndpointsREST

For Agents

Programmatically get account details, create or update account metadata. Covers 46 operations with bearer authentication.

Use for: I need to account details, I want to or update account metadata, Search for account metadata, Find all account metadata

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

Text In Church messaging and contact management API for church communications, including messaging, contacts, groups, calls, workflows, and connect cards. The API exposes 46 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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

30%

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.

72%

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: B-Signals: 1

60%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

37%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Text In Church API to your agent

Capabilities

Start building with Text In Church API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Text In Church API

Jentic AI Readiness Score

Text In Church 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