Convert numbers to their Arabic text representation
Full LLM thinking from the 4-phase benchmark pipeline.
```json
{
"service_type": "platform",
"base_url": "https://tafqit.com",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {
"type": "unknown",
"details": {}
},
"rate_limits": {},
"capabilities": [
"Convert numbers to Arabic text representation",
"Arabic numeral-to-words conversion",
"Likely supports currency amounts (e.g., amounts in riyals, dinars) for checks and invoices",
"Useful for financial documents requiring text amounts in Arabic"
],
"raw_analysis": "Tafqit (تفقيط) is an Arabic-language utility service that converts numeric values into their written Arabic text form. The term 'tafqit' specifically refers to the practice of writing out monetary amounts in words, which is a common requirement on Arabic checks, invoices, contracts, and financial documents to avoid ambiguity and tampering.\n\nMaturity: Little is publicly known about the service beyond its core function. No public REST API documentation, authentication scheme, rate limits, or pricing details were provided in the given description. The service is categorized as 'api,' implying an API is intended to exist, but no endpoint specifications were listed.\n\nTarget audience: Arabic-speaking developers, financial software systems, e-invoicing platforms (e.g., ZATCA-compliant systems in Saudi Arabia), and applications generating formal documents in Arabic.\n\nIntegrations: No documented integrations were provided. Typical usage would be via HTTP calls from applications that generate invoices, receipts, or legal documents.\n\nGiven the minimal information, this appears to be a niche, single-purpose utility. Its actual API surface must be discovered by inspecting the site directly (e.g., /api, /docs, /v1 paths). Without further details, only capabilities can be inferred from the description."
}
```2/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 408ms |
| robots_txt | GET /robots.txt | 200 | 399ms |
| llms_txt | GET /llms.txt | 404 | 379ms |
```json
{
"overall": 52,
"dimensions": {
"token_efficiency": 8.5,
"first_try_success": 6.5,
"response_parseability": 4.0,
"error_clarity": 4.5,
"doc_quality": 4.5,
"auth_simplicity": 7.0,
"latency": 9.5,
"consistency": 6.5
},
"pricing_normalized": {
"type": "unknown",
"notes": "No pricing information detected; likely free/no-login utility. Cannot compare to tiered SaaS pricing."
},
"issues": [
"No public API documented — agents cannot programmatically call the conversion; would need scraping or a headless browser.",
"No llms.txt (404) — no machine-readable guidance for LLM agents.",
"No security headers detected on responses.",
"Pricing model unknown; no transparency on rate limits or commercial use.",
"Documentation quality unclear; only a sitemap and robots.txt were discoverable.",
"Arabic-only interface limits discoverability for English-first agents/users."
],
"recommendations": [
"Publish llms.txt describing the tool, its capabilities, and any API endpoints.",
"Expose a simple JSON API (e.g., /api/tafqit?number=1234¤cy=SAR) returning structured output — this would dramatically raise parseability and first-try success.",
"Add security headers (HSTS, CSP, X-Content-Type-Options) to improve trust signals.",
"Document rate limits, allowed use, and pricing/free tier clearly.",
"Provide an English version or bilingual docs for broader agent discovery.",
"Add OpenAPI/Swagger spec if an API exists or is planned."
]
}
```Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.
<a href="https://prowl.world/service/tafqit">
<img src="https://prowl.world/badge/tafqit.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard