canonical: https://jentic.com/apis/tafqit.herokuapp.com/tafqit-herokuapp

# Tafqit

Convert numbers to their Arabic text representation. The API exposes 1 endpoints.

## For AI agents

Programmatically convert. Covers 1 operations.

## Scope

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

## Capabilities

- convert
- Manage developer tools data programmatically
- Integrate Tafqit into automated workflows
- Query and filter Tafqit records by parameters
- Monitor Tafqit operational status and events

## Use cases

### Developer Tools Operations

Use the Tafqit to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including convert.

Example prompt: Call POST /convert to convert

### Data Retrieval and Monitoring

Query Tafqit 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 Tafqit endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Tafqit 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/convert` | convert |

## Key resources

- **Convert** — Operations for convert

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 41 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/tafqit.herokuapp.com/tafqit-herokuapp/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Tafqit by hand means standing up an HTTP client and shaping the conversion request to its single endpoint yourself, even though it needs no auth. Through Jentic you install once, import Tafqit from the API Directory, and your agent calls it.
- **Permission scoping:** Tafqit exposes a single conversion operation that carries its input in the request body, so limit the agent to the operation it needs, the convert call, rather than to any one resource. That operation runs only because you allowed it.
- **Credential handling:** Tafqit needs no credential, so there is nothing for the agent to hold: your own Jentic One instance calls the operation directly at execution time. No secret enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'convert a number to words', and Jentic returns the matching Tafqit 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 Tafqit use?

The Tafqit uses no authentication. 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 convert with the Tafqit?

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

### What are the rate limits for the Tafqit?

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 convert through Jentic?

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

### How many endpoints does the Tafqit have?

The Tafqit exposes 1 endpoints covering convert operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and Tafqit exposes only a single conversion operation, the POST /convert call. You can allow the agent that one operation and nothing else, so it can convert numbers to their Arabic text representation but cannot reach any other action. That convert call runs only because you permitted it.