← Back to documentation

AI Tool Documentation

Schema for AI tool entries in the AI Manifesto directory

JSON SchemaTypeScript Definitions

Introduction

Understanding the Tool model schema

This page documents the complete schema for the Tool model in The AI Manifesto directory. Use this reference when:

  • Creating tools via the API
  • Building MCP integrations
  • Understanding data validation rules
  • Importing/exporting tool data
name required
String

Name of the AI tool

Validation Rules
Min length:1
Max length:255
Example Values
ChatGPTMidjourneyClaude
description required
String

Brief description of the tool (1-2 sentences)

Validation Rules
Min length:1
Example Values
AI assistant by Anthropic with 200K context windowText-to-image AI model that creates art from descriptions
website_url required
String (uri)

Main website URL for the tool

Validation Rules
Max length:500
Pattern:^https?://
Example Values
https://claude.aihttps://chat.openai.comhttps://midjourney.com
category required
String

Category name (will be created if it doesn't exist)

Validation Rules
Min length:1
Max length:255
Example Values
AI AssistantsCode GenerationImage GenerationVideo EditingWriting Tools

Complete Examples

Full tool objects showing all fields in context

Example 1: Claude

{
  "name": "Claude",
  "description": "AI assistant by Anthropic with 200K context window",
  "long_description": "Claude is an AI assistant created by Anthropic that excels at complex reasoning, coding, and analysis tasks.",
  "website_url": "https://claude.ai",
  "documentation_url": "https://docs.anthropic.com",
  "logo_url": "https://claude.ai/logo.png",
  "reddit_url": "https://reddit.com/r/ClaudeAI",
  "community_url": "https://discord.gg/anthropic",
  "reviews_url": "https://www.g2.com/products/claude/reviews",
  "category": "AI Assistants",
  "pricing_model": "freemium",
  "price_description": "$20/month for Pro plan, free tier available",
  "features": [
    "200K context window",
    "Artifacts for code generation",
    "Computer use capabilities",
    "Vision and document analysis"
  ],
  "use_cases": [
    "Code generation and review",
    "Research and analysis",
    "Content creation",
    "Technical writing"
  ],
  "integrations": [
    "API",
    "Web interface",
    "Mobile apps"
  ],
  "ryan_rating": 9,
  "ryan_notes": "Best AI assistant for coding and complex analysis tasks",
  "ryan_last_used": "2025-11-11",
  "is_featured": true,
  "is_active": true
}

Example 2: Lovable

{
  "name": "Lovable",
  "description": "AI-powered full-stack web app builder",
  "website_url": "https://lovable.dev",
  "category": "Code Generation",
  "pricing_model": "freemium",
  "price_description": "Free tier, paid plans from $20/month",
  "features": [
    "Full-stack app generation",
    "React + TypeScript",
    "Supabase integration"
  ],
  "use_cases": [
    "Rapid prototyping",
    "MVP development"
  ],
  "ryan_rating": 8,
  "is_featured": false,
  "is_active": true
}

Quick Reference

Key points to remember

✅ Required Fields (4)

  • name - Tool name
  • description - Brief description
  • website_url - Official website
  • category - Category name

💡 Best Practices

  • Keep descriptions concise (1-2 sentences)
  • Use long_description for detailed info
  • Include pricing_model when known
  • Add features array for key capabilities

The AI Manifesto © 2025