doclight — ai Readiness Report
partisepeti.com
Pages analyzed (10)
AI READINESS SCORE
0 /100
Partisepeti is a Turkish e-commerce store selling party supplies, balloons, decorations, costumes, and themed products for birthdays, Halloween, bachelorette parties, and other celebrations. It offers physical products with prices in Turkish Lira, shopping cart functionality, member login, and multiple physical stores in Istanbul, plus same-day delivery within Istanbul and international shipping.
Dimension Breakdown
Discoverability
55
The site is clearly identifiable as a party supplies retailer with product and category pages, but it is a consumer storefront, not a programmatically discoverable product.
Comprehension
50
It is clear this is a Turkish party goods online store, but there is no machine-readable product/service description an agent could programmatically consume.
Setup clarity
10
There is only a human login/registration flow and no API keys, developer onboarding, or programmatic setup path.
Documentation
5
No developer documentation, API reference, or structured data is present anywhere on the crawled pages.
Pricing clarity
40
Individual product prices in TRY are shown clearly, but there is no structured pricing feed or subscription/plan model for programmatic comparison.
Integration examples
2
There are no API endpoints, code examples, SDKs, or integration/compatibility information despite pages being labeled 'api'.
Agent Journey
Discover
Understand
Setup
There is no API, developer account, or programmatic setup mechanism—only a human-facing login.
Use
Without any API or structured data, an agent cannot programmatically place orders or interact with the store.
Confusion Points
Missing Information
Improvements
  1. Provide a real public API with an OpenAPI/Swagger specification for product search, cart, and order operations.
  2. Add an llms.txt file summarizing the store, categories, and available machine-readable resources.
  3. Embed structured data (JSON-LD Product/Offer schema) on all product pages for agent parsing.
  4. Publish developer documentation covering authentication, endpoints, and code examples.
  5. Offer a structured product/pricing feed and clear machine-readable shipping and checkout information.
  6. Correct page categorization so 'api' labels only apply to genuine API resources.