Wire it up

Let your Lovable project read this site.

Everything here is open JSON — no key, no auth, no rate card. Paste one block into your project's knowledge file and the agent can look up all 516 tools and the live model feed on its own.

1 · Knowledge file block

# Tool selection knowledge

When this project needs a third-party service, consult the Kbaise directory
before inventing an integration.

- Directory JSON: https://kbaise.com/api/public/tools
- Single tool:    https://kbaise.com/api/public/tools/<slug>
- Model news:     https://kbaise.com/api/public/models
- Weekly digest:  https://kbaise.com/api/public/digest?format=text

Field meanings on a tool record:
- what  — what the tool is, in a sentence or two.
- why   — why you'd pick it over the alternatives.
- warn  — the trap: free-tier caps, lock-in, known failure modes.
- tier  — free | mixed | paid ("mixed" = usable free tier with paid ceilings).
Prose fields are plain text by default; add ?html=1 if you want the markup.

Rules:
1. Prefer a tool whose "tier" is "free" when the project has no budget stated.
2. Always read the "warn" field before committing to a tool — it lists the trap.
3. /api/public/models is a release-news feed (provider, title, summary, link),
   not a list of callable model IDs. Use it to check what shipped recently, then
   confirm the exact model string in the provider's own docs before writing it.
4. Cite the tool slug in your plan so the choice is reviewable.

2 · One-shot prompt

Fetch https://kbaise.com/api/public/tools and pick the best free tool for <what you need>. Read its "warn" field aloud before you write any code, then implement it.

3 · Terminal check

curl -s https://kbaise.com/api/public/tools | jq '.tools[] | select(.tier=="free") | {name, tagline, url}' | head -40

4 · MCP server (Claude Code, Cursor, any MCP client)

{
  "mcpServers": {
    "kbaise": {
      "type": "http",
      "url": "https://kbaise.com/api/public/mcp"
    }
  }
}

# Claude Code one-liner:
claude mcp add --transport http kbaise https://kbaise.com/api/public/mcp

# Tools it exposes: search_tools, get_tool, recommend_stack, audit_stack, compare_tools,
# latest_model_updates, community_stacks, trending_tools, decision_history, weekly_digest
# No key, no account, no rate card.

Full tool list and setup notes on the MCP server page.

Endpoint reference

GET /api/public/tools

Full directory. Filter with ?q=, ?cat=, ?tier=free, ?limit=. Prose fields are plain text; add ?html=1 for markup.

GET /api/public/tools/<slug>

One tool with full write-up, pricing and warnings. Plain text by default; ?html=1 keeps the markup.

GET /api/public/models

Release news from the providers, newest first — headlines and links, not callable model IDs.

GET /api/public/digest?days=7|&week=YYYY-MM-DD|&archive=1

This week in one payload: releases, broken links, drifted dossiers, trending lookups, new community work. Add &format=text for a paste-ready brief.

GET /api/public/pulse

Anonymous aggregate demand: most looked-up tools (7d) and most-run comparisons (30d).

GET /api/public/recommend?task=…

Describe a build, get a stack by role. Add &format=prompt for a paste-ready brief.

GET|POST /api/public/audit

Audit an existing stack: POST { "stack": "<package.json>" }. Add "format":"text" for the brief.

GET|POST /api/public/compare?slugs=a,b

Two to four tools head to head. Add &format=text for the raw brief.

GET /api/public/stacks

Stacks published by builders, most endorsed first. Add ?sort=new or ?limit=.

GET /api/public/stacks/<id>

One stack: tools by role, traps, and a brief. Add ?format=text for the raw brief.

POST /api/public/mcp

MCP server (JSON-RPC 2.0). GET the same URL for a manifest.

Responses are cached for five minutes and CORS-open, so browser-side agents work too.