canonical: https://jentic.com/apis/stc.com.sa/stc-com-sa

# STC Developer API

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

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

### Developer Tools Operations

Use the STC Developer API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including create payment, get payment status.

Example prompt: Call POST /payments to create payment

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

Example prompt: 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.

Example prompt: Search Jentic for 'create payment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payments` | Create payment |
| GET | `/payments/{id}` | Get payment status |

## Key resources

- **Payments** — Operations related to Payments

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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