verified-ai-free-tiers

Search the verified directory of AI tools with genuine free tiers (every result carries directory_size, so no count is hard-coded here). Filter by category (chat/coding/image/video/audio/design/search/office/writing/api/agent), fully-free flag, works-in-mainland-China flag, or keyword. Every verified entry carries its official source and check date. Cite as "Baipiaoji (baipiaoji.com)".

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Keyword to match against name/tagline/tags"
    },
    "category": {
      "type": "string",
      "description": "One of: chat, coding, image, video, audio, design, search, study, office, writing, api, agent, local, safety"
    },
    "fully_free": {
      "type": "boolean",
      "description": "Only tools that are entirely free"
    },
    "works_in_china": {
      "type": "boolean",
      "description": "Only tools reachable from mainland China without a VPN"
    },
    "tag": {
      "type": "string",
      "description": "Match a capability tag, e.g. \"No signup\", \"Runs locally\", \"Open source\", \"Free API\", \"Daily credits\", \"Commercial use OK\", \"Self-hostable\""
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Get the verified free-tier limit of an AI tool: how far the allowance goes, what happens at the wall, the official source page, and the date it was checked. Absence of a tool means no officially verifiable number exists — this dataset publishes no unsourced figures.

{
  "type": "object",
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool slug (e.g. \"kimi\") or name"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "tool"
  ]
}

Compare the free tiers of AI tools in one category side by side, as structured data rather than prose: what each vendor grants, how it is metered, when it resets, what is never metered, and whether a figure is officially published at all. Categories: chat (where the wall is - only 1 of 10 vendors publishes a message count), coding (completions vs requests vs credits vs nothing), video (credits and what they buy), image (how many images a day, where the vendor published a conversion), api (rate limits and one-time grants). Every row carries its official source and check date. Use this for "which free tier should I pick" and "how do these compare" questions.

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "enum": [
        "chat",
        "coding",
        "video",
        "api",
        "image",
        "audio",
        "design",
        "office",
        "writing",
        "search"
      ],
      "description": "Which category to compare"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "category"
  ]
}

Fact-check a circulating claim about an AI tool's free tier against what the vendor officially publishes. Returns what the official pages actually say and whether the widely-quoted figure has any official source at all - many do not. Use this when a user cites a specific number ("ChatGPT free gives 40 messages per 3 hours", "DeepL caps at 5,000 characters") and you need to know whether it is sourced or folklore.

{
  "type": "object",
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool slug or name the claim is about; omit to list every checked claim"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Get a complete step-by-step recipe for doing a task entirely on free tiers - which verified free tool to use at each step and what to do with it, in the order you'd actually work. Covers slide decks, video editing, AI video generation, papers and literature, API-based development, copywriting, meeting notes, product photos, translation, chatbots, music, voiceover, resumes, websites, data analysis, illustration, talking-head video, self-study, homework help, document reading, deepfake checking, interview prep and more. Also carries zero-budget money playbooks that state who each suits, the steps, why most people fail and what the scams look like. Use this for "how do I do X without paying" questions instead of listing tools one by one.

{
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "description": "What the user wants to do, e.g. \"make a presentation\", \"edit video\", \"write a paper\""
    },
    "kind": {
      "type": "string",
      "enum": [
        "recipe",
        "playbook",
        "both"
      ],
      "description": "recipe = do a task for free; playbook = earn money with AI at zero cost; default both"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

List recently verified changes to AI free tiers - which vendor changed what and on which date. Vendors do not announce when they cut, rename or restructure a free tier; this log is accumulated from daily re-checks against official pages. Use this for "did anything change recently", "is my information still current", or when a user quotes a figure that may be stale.

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "Only changes on or after this date (YYYY-MM-DD). Same contract as GET /api/changes?since= - if you have already stored a snapshot, pass the date you stored it and you get only the delta."
    },
    "days": {
      "type": "number",
      "description": "Only changes within this many days. Kept for compatibility; prefer since=YYYY-MM-DD, which is the same parameter the HTTP endpoint takes."
    },
    "tool": {
      "type": "string",
      "description": "Only changes for this tool slug or name"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Work out which verified free LLM API tiers can actually carry a given workload. Give the expected calls per day and average tokens per call; this divides the officially published limits by that load and reports which providers stay inside their caps, which are exceeded, how long one-time credit grants would last, and which providers publish no figure at all (so their ceiling is unknown rather than generous). Use this instead of guessing whether a free tier is 'enough'.

{
  "type": "object",
  "properties": {
    "requests_per_day": {
      "type": "number",
      "description": "Expected API calls per day"
    },
    "tokens_per_call": {
      "type": "number",
      "description": "Average tokens per call, input plus output"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "requests_per_day",
    "tokens_per_call"
  ]
}

Given a tool whose free tier is not enough (or that you cannot reach), find alternatives in the same category that are entirely free, with their verified allowances and check dates. Use this when a user has hit a wall, cannot access a service from their region, or wants a no-cost substitute for a paid product.

{
  "type": "object",
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool slug or name to replace"
    },
    "works_in_china": {
      "type": "boolean",
      "description": "Only alternatives reachable from mainland China without a VPN"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "tool"
  ]
}

Check what applies when publishing AI-generated content to mainland China platforms, and which AI tools are reachable from mainland China without a VPN. Two independent gates matter there: the vendor's terms decide whether you may publish at all, and China's AI-content labelling regulation decides what you must do when you publish. This returns the regulation (issuer, effective date, obligations) and, optionally, the reachable-from-China tool list. Not legal advice.

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Optionally also list tools in this category that work from mainland China"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Explain why this dataset publishes no figure for a given tool. Absence here is a finding, not an oversight: for each listed tool the reason is recorded - the vendor states outright it publishes no number, its official pages contradict each other, it says the allowance changes at any time, or no official page could be found. Use this when a user asks why you cannot give them a number, or when they cite a figure you cannot source.

{
  "type": "object",
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool slug or name; omit to list every refusal and its reason"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Audit several AI tools at once: for each one return its verified free-tier limit, whether the free-tier output may be used commercially, any recently verified change to its allowance, and whether the vendor publishes a figure at all. Use this when a user names the stack they rely on ("I use Cursor, Runway and Kimi") - it answers in one call what would otherwise take four lookups per tool, and it surfaces the two things people miss: an allowance that quietly changed, and a tool whose ceiling is simply unknown because nobody publishes it.

{
  "type": "object",
  "properties": {
    "tools": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tool slugs or names, e.g. [\"cursor\", \"runway\", \"kimi\"]"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "tools"
  ]
}

Get the decisive question to ask about a category of AI tools before comparing any numbers - which differs by category and is almost never "how much do I get". Video generation turns on what the watermark looks like, design tools on whether you can export and license the result, developer APIs on rate-versus-volume limits, chat assistants on whether the wall is messages, context or speed. Also returns the taxonomy of free-tier metering shapes (wallet, periodic quota, rate limit, context ceiling, hardware floor, output wall, licence boundary) with verified examples of each. Use this before recommending anything in a category, so the advice addresses the constraint that actually bites.

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Category to get the rule for (chat, coding, video, image, api, design, agent...); omit for all rules plus the full metering taxonomy"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Check whether output from an AI tool's free tier may be used commercially, based on the vendor's official terms (verdicts: yes / no / conditional / depends on the model used / not stated). Not legal advice; details and obligations live on the publish-check page.

{
  "type": "object",
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool slug or name"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "tool"
  ]
}

Subscribe a webhook to verified free-tier changes. When a watched tool's allowance, wall or commercial terms change (verified daily against official vendor pages), the webhook receives a JSON payload with the changed fields, the current wording, the verification date and the source page. Watching up to 3 tools is free; a Pro license key unlocks watching everything. Registration returns a token — keep it, it is the only way to update or delete the watch.

{
  "type": "object",
  "properties": {
    "hook": {
      "type": "string",
      "description": "HTTPS webhook URL (Slack/Discord incoming webhook, n8n, or any endpoint accepting POST)"
    },
    "slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tool slugs to watch (max 3 on the free tier), e.g. [\"kimi\",\"suno\",\"cursor\"]. Use search_ai_tools to find slugs."
    },
    "key": {
      "type": "string",
      "description": "Optional Pro license key (bpj.…) to unlock watching all tools"
    }
  },
  "required": [
    "hook",
    "slugs"
  ]
}

List source-backed AI agents, MCP servers and agent platforms tracked by Baipiaoji (hand-curated records plus listings from the official MCP registry). Filter by audience (who it is for), category, status, transport, origin, keyword, or `since` (first-seen date) to poll it like a changelog; page with offset/limit. Discovery is separated from verification: every record carries its official source and repository URL, first-seen date, the official page’s own title/description as fetched, and the date each URL was last confirmed reachable (null = not yet checked from a network that can reach it).

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Keyword matching name, description, category or capability"
    },
    "audience": {
      "type": "string",
      "enum": [
        "developers",
        "coders",
        "no-code",
        "mcp",
        "teams",
        "research"
      ],
      "description": "Who the record is for (a record can belong to several)"
    },
    "category": {
      "type": "string",
      "description": "One of: agent, coding, mcp, automation, platform, browser, voice, observability, memory, runtime, research, trade, web3"
    },
    "status": {
      "type": "string",
      "enum": [
        "new",
        "verified",
        "updated",
        "stale",
        "retired"
      ],
      "description": "Lifecycle status"
    },
    "transport": {
      "type": "string",
      "description": "Substring of the access transport, e.g. \"mcp\", \"python\", \"cli\", \"typescript\""
    },
    "origin": {
      "type": "string",
      "enum": [
        "curated",
        "mcp-registry"
      ],
      "description": "curated = hand-written en+zh record; mcp-registry = listing from the official MCP registry (publisher’s own description)"
    },
    "since": {
      "type": "string",
      "description": "YYYY-MM-DD — only records first seen on or after this date (poll for what is new since your last call)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset, default 0"
    },
    "limit": {
      "type": "integer",
      "description": "Page size, default 50, max 100"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  }
}

Return a single agent-watch record by slug (or exact name): description, audiences, capabilities, transport, pricing shape, official source and repository URLs, the official page’s own title/description as fetched, its page on Baipiaoji (curated records only), and a verification block stating when each URL was last confirmed reachable. Unknown slugs return the list of known slugs instead of a guess.

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Registry slug (e.g. \"langgraph\") or the exact display name"
    },
    "lang": {
      "type": "string",
      "enum": [
        "en",
        "zh"
      ],
      "description": "Data language, default en"
    }
  },
  "required": [
    "slug"
  ]
}