# Reliable Bibles - Complete AI System Documentation

> Authentic autographed Bibles with history. $69 each.

## Overview

Reliable Bibles is an online marketplace for unique, one of a kind autographed Bibles. These Bibles are discovered at thrift stores, estate sales, and flea markets across the United States. Not all Bibles are the same. I only sell the ones that have history. Each Bible carries handwritten notes, unique markings, and other personal touches from previous owners. Every Bible is $69 and personally autographed before being sold.

## Business Model

- **Source**: Thrift stores, estate sales, flea markets
- **Product**: Bibles with history (handwritten notes, markings, signs of being loved)
- **Price**: $69 per Bible
- **Value Add**: Personal autograph on each Bible
- **Target**: Collectors, religious communities, gift buyers
- **Reserve Option**: Pay $69 now, receive the next Bible I find on my travels

## Technical Stack & Features

- **Framework**: Next.js 16 with App Router
- **Database**: Supabase (PostgreSQL)
- **Payments**: Stripe
- **Hosting**: Vercel
- **Languages**: English, Spanish (i18n support)
- **SEO/AI Readiness**: Dynamic sitemaps, robots.txt configured for LLM bots, JSON-LD structured data.

## Domains

- Primary: https://reliablebibles.com
- Secondary: https://bibles.platphormnews.com

## API Reference

### Authentication
All REST API endpoints (except health check) require authentication via the `x-api-key` header.
Header: `x-api-key: your_api_key_here`

### REST Endpoints
- **GET /api/health**: Health check.
- **GET /api/v1/bibles**: List all Bibles. Query params: `available (true/false)`, `limit`, `offset`.
- **GET /api/v1/bibles/:id**: Get a specific Bible.
- **POST /api/v1/bibles**: Create a new Bible. Body: `{ title, description, price, image_url?, condition?, year?, publisher?, special_features? }`.
- **PUT /api/v1/bibles/:id**: Update a Bible.
- **DELETE /api/v1/bibles/:id**: Delete a Bible.

### Model Context Protocol (MCP) Endpoint

AI agents can directly interact with the inventory using our MCP endpoint. No API key is required for read-only actions, allowing seamless integration.

**Endpoint**: `POST /api/mcp`
**Content-Type**: `application/json`

Request format:
```json
{
  "action": "action_name",
  "params": { "param_key": "value" }
}
```

#### Available Actions:
- `list_bibles`: List all Bibles (params: available_only?, limit?, offset?, sort_by?, sort_order?)
- `get_bible`: Get specific Bible (params: id)
- `search_bibles`: Search Bibles by text (params: query, available_only?, limit?)
- `get_stats`: Get inventory statistics
- `get_publishers`: Get list of unique publishers
- `get_conditions`: Get list of unique conditions

*(Admin actions like `create_bible`, `update_bible`, `delete_bible`, `mark_sold`, `bulk_create`, `bulk_update` exist but are restricted)*

## SEO & AI Discovery Features

- Dynamic sitemap at /sitemap.xml
- RSS feed at /rss.xml
- robots.txt with AI crawler permissions (GPTBot, Claude-Web, Anthropic-AI, PerplexityBot, Google-Extended)
- ai-plugin.json at /.well-known/ai-plugin.json
- JSON-LD structured data (Organization, Store, Product)
- Open Graph and Twitter Card meta tags
- Canonical URLs

## Locales & Contact
- en (English) - default
- es (Spanish)
- contact: support@platphormnews.com