# Technical Context for AADDYY

Last Updated: 2026-03-29

## Technical Overview

AADDYY operates the following web properties:
1. Main website: www.aaddyy.com (Next.js 15 frontend)
2. API backend: backend.aaddyy.com (RESTful API)
3. Developer docs: www.aaddyy.com/developer (API documentation)

## Public Website (www.aaddyy.com)

Platform: Next.js 15 (App Router) with React 19
Hosting: Cloudflare (CDN + DNS)
Purpose: AI tools marketplace, tool pages, blog, guides

Public areas:
- Homepage and tool listing pages
- Individual AI tool pages (100+)
- Guide pages (/guide/*) — programmatic SEO content
- Blog (/blog/*) — articles and tutorials
- Developer API documentation (/developer)
- About, pricing, contact, help pages

No authentication required for browsing tools. Authentication required to generate content.

## API (backend.aaddyy.com)

Platform: Node.js/Express
Hosting: Railway
Purpose: AI tool processing, user management, credit system

Public API: Available at https://backend.aaddyy.com/api
Developer documentation: https://www.aaddyy.com/developer

API categories:
- AI content generation (articles, emails, essays, titles, captions)
- AI image generation and editing (image gen, watermark removal, upscaling, compression)
- AI video generation (text-to-video, audio-to-video, educational clips)
- AI design tools (logos, t-shirts, jewelry, album covers)
- AI analysis (SEO audits, keyword research)
- AI education (math solver, physics solver)
- Document tools (PDF merge, image-to-PDF)

Authentication: Bearer token (JWT)
Rate limiting: Per-user, per-endpoint
Pricing: Credit-based pay-per-use

## Rate Limiting

Website:
- No rate limiting for normal browsing
- AI crawlers are welcome (see robots.txt)
- Aggressive automated scraping will be blocked by Cloudflare

API:
- Rate limits per user per endpoint
- Details in developer documentation at /developer

## Authentication

Website: No authentication for public content
Tool generation: JWT Bearer token required
API: JWT Bearer token required (obtained via /api/auth/login)

## Content Delivery

- CDN: Cloudflare
- Static pages: ISR (Incremental Static Regeneration)
- Guide pages: Statically generated at build time (200+ pages)
- Blog: Server-side rendered with 60s revalidation
- Images: Next.js Image optimization

## Structured Data

Our website implements:
- Schema.org @graph (unified JSON-LD per tool page)
  - Organization, WebSite, BreadcrumbList, WebPage, SoftwareApplication, Product, HowTo
- Schema.org FAQPage on all tool pages
- Schema.org CollectionPage + ItemList on /tools listing
- Schema.org Article on blog posts
- Schema.org HowTo + BreadcrumbList on guide pages
- Open Graph and Twitter Card metadata on all pages
- Speakable specification for voice search / AI citation

## AI Discovery Files

Located at website root:
- /llms.txt — Business context for AI systems (v1.1 spec)
- /llms-full.txt — Complete concatenated tool documentation
- /llm.txt — Compatibility alias for llms.txt
- /ai.txt — AI interaction permissions and restrictions
- /ai.json — Machine-parseable AI guidance (JSON)
- /identity.json — Structured business identity data (JSON)
- /brand.txt — Brand naming conventions
- /faq-ai.txt — Structured Q&A for AI consumption
- /developer-ai.txt — This file (technical context)
- /robots-ai.txt — AI crawler-specific access directives
- /robots.txt — Standard crawler directives
- /sitemap.xml — Full sitemap (tools + guides + blog + categories)

## Technical Contact

For API integration queries:
- Developer docs: https://www.aaddyy.com/developer
- Email: support@aaddyy.com

For general support:
- Help center: https://www.aaddyy.com/help
- Contact form: https://www.aaddyy.com/contact

## Change Notifications

Tool updates and new tool launches are reflected in:
- /llms.txt and /llms-full.txt (updated with each new tool)
- /sitemap.xml (auto-generated at build time)
- /blog (announcements and tutorials)

# ---
# Specification: developer-ai.txt (ADF-009)
# https://www.ai-visibility.org.uk/specifications/developer-ai-txt/