Install Jentic One Beta

Connect the SlickText API to your agent

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

Retrieve brand information

Create a contact

Edit a specific contact

Delete a specific contact

Monitor SlickText API operational status and events

GET STARTED

Start building with SlickText API

Explore with Jentic One

View OpenAPI Document

Automated Brands Management

Automate brands operations by combining multiple SlickText API endpoints. Agents can retrieve credit usage from brand and then create a contact in a single workflow.

Call GET /brands/{brand_id}/usage to retrieve credit usage from brand, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SlickText 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 'retrieve brand information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

21 endpoints — sms marketing and text messaging api for managing brands, contacts, campaigns, lists, and messaging workflows.

METHOD

PATH

DESCRIPTION

GET

/brands

Retrieve brand information

GET

/brands/{brand_id}/usage

Retrieve credit usage from brand

POST

/brands/{brand_id}/contacts

Create a contact

GET

/brands/{brand_id}/contacts

Retrieve all contacts

GET

/brands/{brand_id}/contacts/{id}

Retrieve a specific contact

PUT

/brands/{brand_id}/contacts/{id}

Edit a specific contact

DELETE

/brands/{brand_id}/contacts/{id}

Delete a specific contact

POST

/brands/{brand_id}/campaigns

Create a campaign

GET

/brands

Retrieve brand information

GET

/brands/{brand_id}/usage

Retrieve credit usage from brand

POST

/brands/{brand_id}/contacts

Create a contact

GET

/brands/{brand_id}/contacts

Retrieve all contacts

GET

/brands/{brand_id}/contacts/{id}

Retrieve a specific contact

PUT

/brands/{brand_id}/contacts/{id}

Edit a specific contact

DELETE

/brands/{brand_id}/contacts/{id}

Delete a specific contact

POST

/brands/{brand_id}/campaigns

Create a campaign

Why Jentic?

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

Setup

Wiring the SlickText API by hand means sending a bearer token in the Authorization header to dev.slicktext.com/v1 and managing the brands, contacts, and campaigns calls yourself. Through Jentic you install once, import SlickText from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

SlickText puts the brand id and contact id in the URL path (/brands/{brand_id}/contacts/{id}), so a rule can pin your agent to one brand. You choose the operations it may call, so destructive ones like contact deletion are not included unless you add them.

Credential isolation

Your SlickText bearer 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 'add a contact to a brand' or 'create a campaign', and Jentic returns the matching SlickText operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SlickText API through Jentic.

What authentication does the SlickText API use?

The SlickText 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 retrieve brand information with the SlickText API?

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

What are the rate limits for the SlickText 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 retrieve brand information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve brand information'. Jentic returns the matching SlickText API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the SlickText API have?

The SlickText API exposes 21 endpoints covering brands operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which SlickText operations and credentials the agent may use. SlickText carries the brand id and contact id in the URL path, such as /brands/{brand_id}/contacts/{id}, so you can pin the agent to a single brand and choose exactly which endpoints it may call. Destructive operations like DELETE on a contact stay out of reach unless you explicitly grant them.

SlickText API

Name: SlickText API
Brand: SlickText API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer21 EndpointsREST

For Agents

Programmatically retrieve brand information, retrieve credit usage from brand. Covers 21 operations with bearer authentication.

Use for: I need to brand information, I want to credit usage from brand, Search for a contact, Find all all contacts

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

SMS marketing and text messaging API for managing brands, contacts, campaigns, lists, and messaging workflows. The API exposes 21 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: ASignals: 4

97%

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).

50%

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: D+Signals: 4

31%

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.

66%

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

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SlickText API to your agent

Capabilities

Start building with SlickText API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SlickText API

Jentic AI Readiness Score

SlickText 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