Install Jentic One Beta

Connect the QuickSend SMS API to your agent

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

Send a single SMS

Check account balance

Access QuickSend SMS API communications resources via REST API

Use Cases

Patterns agents use QuickSend SMS API for, with concrete tasks.

★ Communications Operations

Use the QuickSend SMS API to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including send a single sms, send bulk sms with same message, send bulk sms with different messages.

GET STARTED

Start building with QuickSend SMS API

Explore with Jentic One

View OpenAPI Document

Automated SMS Management

Automate sms operations by combining multiple QuickSend SMS API endpoints. Agents can send bulk sms with same message and then send bulk sms with different messages in a single workflow.

Call GET /api.php#sendBulkSame to send bulk sms with same message, then verify the result

AI Agent Integration via Jentic

AI agents discover and call QuickSend SMS 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.

Search Jentic for 'send a single sms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — quicksend is an sms gateway solution for sri lanka.

METHOD

PATH

DESCRIPTION

GET

/api.php

Send a single SMS

GET

/api.php#sendBulkSame

Send bulk SMS with same message

GET

/api.php#sendBulkDifferent

Send bulk SMS with different messages

GET

/api.php#checkBalance

Check account balance

GET

/api.php

Send a single SMS

GET

/api.php#sendBulkSame

Send bulk SMS with same message

GET

/api.php#sendBulkDifferent

Send bulk SMS with different messages

GET

/api.php#checkBalance

Check account balance

Why Jentic?

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

Setup

Wiring QuickSend SMS by hand means passing its up key as a query parameter, targeting the quicksend.lk/Client host, and handling retries across its send and balance operations yourself. Through Jentic you install once, import QuickSend SMS from the API Directory, store the API key once, and your agent calls it.

Permission scoping

QuickSend SMS drives sends and balance checks through query parameters on a single api.php endpoint, so limit the agent to the operations it needs, such as sending a single message or checking the balance. You choose which operations are allowed, so bulk sends are not reachable unless you add them.

Credential isolation

Your QuickSend SMS 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.

Intent-based discovery

Agents search Jentic by intent such as 'send an SMS message' or 'check SMS balance', and Jentic returns the matching QuickSend operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using QuickSend SMS API through Jentic.

What authentication does the QuickSend SMS API use?

The QuickSend SMS API uses an API key passed in the `up` query. 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 a single sms with the QuickSend SMS API?

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

What are the rate limits for the QuickSend SMS 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 a single sms through Jentic?

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

How many endpoints does the QuickSend SMS API have?

The QuickSend SMS API exposes 4 endpoints covering sms, account operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which QuickSend SMS operations the agent may call and which credentials it may use. QuickSend drives every action through query parameters on a single api.php endpoint, so you can allow just sending a single message or checking the account balance and leave the bulk-send operations out entirely. Bulk sends stay unreachable unless you explicitly add them, and your API key is injected only for the calls you have approved.

Quicksend Lk QuickSend SMS API

Name: QuickSend SMS API
Brand: QuickSend SMS API
Availability: InStock

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey4 EndpointsREST

For Agents

Programmatically send a single sms, send bulk sms with same message. Covers 4 operations with apiKey authentication.

Use for: I need to send a single sms, I want to send bulk sms with same message, Search for send bulk sms with different messages, Find all check account balance

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

QuickSend is an SMS Gateway Solution for Sri Lanka. This API allows sending single and bulk SMS messages and checking account balance. The API exposes 4 endpoints secured with apiKey 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

99%

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: CSignals: 4

64%

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.

50%

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: FSignals: 1

15%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the QuickSend SMS API to your agent

Capabilities

Use Cases

Start building with QuickSend SMS API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Quicksend Lk QuickSend SMS API

Jentic AI Readiness Score

QuickSend SMS 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