Install Jentic One Beta

Connect the STC Developer API to your agent

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

Create payment

Get payment status

Integrate STC Developer API into automated workflows

Query and filter STC Developer API records by parameters

Monitor STC Developer API operational status and events

GET STARTED

Start building with STC Developer API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query STC Developer 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.

Poll the primary STC Developer API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call STC Developer 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 'create payment', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — saudi telecom company developer apis.

METHOD

PATH

DESCRIPTION

POST

/payments

Create payment

GET

/payments/{id}

Get payment status

POST

/payments

Create payment

GET

/payments/{id}

Get payment status

Why Jentic?

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

Setup

Wiring the STC Developer API by hand means setting up its X-API-Key header, mapping the payment create and lookup calls, and handling the response shapes yourself. Through Jentic you install once, import the STC Developer API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

You limit the agent to the operations it needs, such as reading a payment by id, so it never creates payments unless you include that operation. Scope the agent by operation to keep it to the calls you intend.

Credential isolation

Your STC 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 'create a payment' or 'get a payment by id', and Jentic returns the matching STC Developer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using STC Developer API through Jentic.

What authentication does the STC Developer API use?

The STC Developer 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 create payment with the STC Developer API?

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

What are the rate limits for the STC Developer 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 create payment through Jentic?

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

How many endpoints does the STC Developer API have?

The STC Developer API exposes 2 endpoints covering payments operations.

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

Yes. Because Jentic One is self-hosted and enforces your own rules, you decide which STC Developer API operations the agent may call and which credentials it may use. You can grant read-only access with GET /payments/{id} to look up a payment by id, and withhold POST /payments so the agent can never create a payment unless you include that operation. Scoping the agent by operation keeps it to exactly the calls you intend.

STC Developer API

Name: STC Developer API
Brand: STC Developer API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey2 EndpointsREST

For Agents

Programmatically create payment, get payment status. Covers 2 operations with apiKey authentication.

Use for: I need to payment, I want to payment status, Get the current status of STC Developer API resources, List all records from STC Developer API

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

Saudi Telecom Company developer APIs. The API exposes 2 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the STC Developer API to your agent

Capabilities

Start building with STC Developer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

STC Developer API