DEVELOPER & AI AGENT REFERENCE Updated

TXCIZ (Cheats4You) API Documentation — REST v1, OpenAPI 3.1, CLI & MCP

Quick Answer & Reference Verified:

TXCIZ provides an unauthenticated, read-only REST v1 JSON API (/api/v1/*), OpenAPI 3.1.0 specification (/openapi.json), per-game Markdown shards (/llms/:productId.md, <8,000 tokens), Streamable HTTP MCP server (/mcp), and zero-dependency txciz-cli (/cli) enforcing 120 req/60s rate limits for live status, Euro pricing, and 49 Windows PC guides.

TXCIZ (Cheats4You) provides an unauthenticated, read-only Application Programming Interface (API), OpenAPI 3.1 schema, per-game Markdown shards, Streamable HTTP Model Context Protocol (MCP) server, and the official TXCIZ CLI (txciz-cli) maintained by the TXCIZ Technical Team.

1. Authentication, Prerequisites & Rate Limits

All TXCIZ public catalog, live status, technical guide, OpenAPI 3.1.0, CLI, and MCP read endpoints operate without API keys (security: []) under a shared 120 req/60s sliding rate limit.

  • Zero API Key Required: All public status, catalog, blog, OpenAPI, and MCP read endpoints operate without authentication tokens (security: []).
  • Explicit API Versioning: Versioned /api/v1/* routes (and legacy /api/* aliases) return X-API-Version: 2026-11-11 for deterministic schema pinning.
  • Binary Stock Masking: Public responses normalize plan stock to 1 (In Stock) or 0 (Out of Stock) and never expose buyer records or checkout sessions.
  • Standard RateLimit Headers: Public read responses include RateLimit, RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy: 120;w=60 headers, plus Retry-After on HTTP 429.

Prerequisites & Expected Response Contract

  • Client Prerequisites: Any HTTP client (curl, fetch, or Node.js 20+) with outbound HTTPS access to https://www.cheats4you.com; zero API keys or bearer tokens needed.
  • Expected Outcome: GET /api/v1/status returns HTTP 200 OK with X-API-Version: 2026-11-11, ETag, RateLimit-Policy: 120;w=60, and typed JSON across all 11 PC titles (text/markdown adds x-markdown-tokens).

2. Versioning & Deprecation Policy

New client and agent integrations must target /api/v1/status, /api/v1/products, and /api/v1/blog. Unversioned /api/status, /api/products*, and /api/blog* routes remain active for backward compatibility, carry deprecated: true in the OpenAPI 3.1.0 schema (GET /openapi.json), and emit RFC 9745 Deprecation: @1798761600, RFC 8594 Sunset: Fri, 31 Dec 2027 23:59:59 GMT, and rel="successor-version" Link headers with a minimum 90-day sunset window.

3. REST JSON, Shards & Schema Endpoints

EndpointOperation IDQuery / Path ParametersPurpose
GET /api/v1/status (/api/status alias)getCatalogStatusV1 / getCatalogStatusfresh (0 or 1)Real-time Undetected, Updating, and Out of Stock summary plus per-title status.
GET /api/v1/products (/api/products alias)listProductsV1 / listProductsstatus, category, game, q, view, fields, limit, offset, freshList all 11 PC game enhancement suites, live status badges, and EUR plans.
GET /api/v1/products/:productId (/api/products/:productId alias)getProductByIdV1 / getProductByIdproductId (e.g. rob-run), freshFetch full specifications, PC requirements, compatibility notes, videos, and changelog.
GET /api/v1/blog (/api/blog alias)listBlogGuidesV1 / listBlogGuidescategory, game, topic, q, view, fields, limit, offset, freshFilter and search all 49 original ESP, radar, and aimbot tuning guides.
GET /api/v1/blog/:slug (/api/blog/:slug alias)getBlogGuideBySlugV1 / getBlogGuideBySlugslugFetch complete guide sections, comparison tables, FAQs, and related articles.
GET /llms/:productId.mdMarkdown ShardproductId (e.g. delta-force)Single-game RAG knowledge bundle (<8,000 tokens) with product specs and game guides.
GET /openapi.json (/api/v1/openapi.json)SchemaNoneFetch the self-describing OpenAPI 3.1.0 JSON schema (GET /openapi.json or GET /.well-known/openapi.json).
POST /mcpcallMcpEndpointJSON-RPC 2.0 bodyConnect MCP hosts (view MCP server guide).
GET /cli (/cli/txciz-cli.tgz)txciz-cliCLI subcommandsScript status, products, and guides via the official TXCIZ CLI.

4. Example Requests, Headers & Sample Output

Send Accept: text/markdown to any public storefront URL, append .md, poll the live REST v1 Status Endpoint, or download txciz-cli.tgz (npm package), the standalone txciz.mjs ESM script, or the full TXCIZ CLI Markdown guide:

curl -sS "https://www.cheats4you.com/api/v1/status"

curl -sS "https://www.cheats4you.com/api/v1/products/rob-run"

curl -sS "https://www.cheats4you.com/llms/rob-run.md"

curl -sS -H "Accept: text/markdown" "https://www.cheats4you.com/products/rob-run"

npx --yes "https://www.cheats4you.com/cli/txciz-cli.tgz" status --json

Sample Response Headers (ETag, RateLimit, X-API-Version & x-markdown-tokens)

Public JSON responses include deterministic caching and IETF rate-limit headers, while Markdown twins and /llms/:productId.md shards also emit x-markdown-tokens for context-window planning:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-API-Version: 2026-11-11
ETag: "7b4a9c2d1f8e3a0b5c6d7e8f9a0b1c2d-id"
RateLimit: "public";r=119;t=60
RateLimit-Limit: 120
RateLimit-Remaining: 119
RateLimit-Reset: 60
RateLimit-Policy: 120;w=60
Vary: Accept-Encoding

# Additional header on Accept: text/markdown or /llms/:productId.md
x-markdown-tokens: 6333

Sample GET /api/v1/status JSON Output

{
  "updatedAt": "2026-11-18",
  "summary": {
    "totalCount": 11,
    "undetectedCount": 10,
    "updatingCount": 1,
    "outOfStockCount": 0,
    "comingSoonCount": 0,
    "onlineDeliveryCount": 10
  },
  "products": [
    {
      "id": "rob-run",
      "name": "Rob Run",
      "version": "v1.4.3",
      "status": "available",
      "statusLabel": "Undetected",
      "inStock": true,
      "startingPriceEur": 6.99,
      "lastVerified": "2026-11-18",
      "shardUrl": "https://www.cheats4you.com/llms/rob-run.md"
    }
  ]
}

5. Caching, ETag Revalidation, Error Triage & Guides

All public GET routes emit deterministic ETag validators alongside Vary: Accept, Accept-Encoding headers so automated pollers can send If-None-Match requests and receive 304 Not Modified with zero duplicate bandwidth when catalog status has not changed.

Public REST responses reflect the exact same live product status, Euro (EUR) plan pricing, and controller compatibility shown on interactive storefront pages (Live Status and Game Catalog), while strictly isolating customer Stripe sessions, email receipts, Order IDs, and license key vaults behind authenticated checkout boundaries.

HTTP Error & Rate-Limit Triage Matrix (400, 404, 429, 503)

HTTP StatusTrigger CauseResponse Headers / BodyRecommended Fix
400 Bad RequestMalformed query parameter or invalid request syntax.JSON { "error": "..." } envelope.Verify allowed enum values (status=all|available|updating|coming_soon, fresh=0|1) from GET /openapi.json.
404 Not FoundUnknown productId slug or blog article slug.JSON { "error": "..." } without stack traces.Fetch canonical slugs dynamically from GET /api/v1/products or GET /api/v1/blog.
429 Too Many RequestsCaller exceeded 120 requests inside a 60-second window.Retry-After seconds + RateLimit headers.Sleep Retry-After seconds and send If-None-Match with ETag so unchanged polls return 304.
503 Service UnavailableTransient upstream catalog sync or maintenance window.Retry-After / JSON error message.Retry with exponential backoff and inspect live operational notes on Live Status.

Frequently Asked Questions

Do TXCIZ public catalog, status, and guide API endpoints require an API key?
No. All read-only status, catalog, technical guide, OpenAPI 3.1, CLI, and MCP endpoints declare security: [] and accept unauthenticated GET or POST requests.
Which REST path prefix should new integrations target?
Target the versioned /api/v1/status, /api/v1/products, and /api/v1/blog endpoints. Unversioned /api/status, /api/products, and /api/blog aliases remain available for backward compatibility and emit RFC 9745 Deprecation and RFC 8594 Sunset headers.
What rate-limit headers are returned on public endpoints?
Public endpoints allow 120 requests per 60-second window and emit RateLimit, RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy (120;w=60) headers, plus Retry-After on HTTP 429.
How do AI agents fetch low-token Markdown twins or single-game RAG shards?
Send Accept: text/markdown on any public storefront route, append .md (for example /products/rob-run.md), run npx --yes https://www.cheats4you.com/cli/txciz-cli.tgz product rob-run --shard, or fetch /llms/rob-run.md for a complete single-game bundle under 8,000 tokens.