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.lovable.app/api/public/tools
- Single tool:    https://kbaise.lovable.app/api/public/tools/<slug>
- Model feed:     https://kbaise.lovable.app/api/public/models
- Weekly digest:  https://kbaise.lovable.app/api/public/digest?format=text

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. Before writing any AI model ID, fetch the model feed and use a model that
   appears there. Never hardcode a model name from memory.
4. Cite the tool slug in your plan so the choice is reviewable.

2 · One-shot prompt

Fetch https://kbaise.lovable.app/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.lovable.app/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.lovable.app/api/public/mcp"
    }
  }
}

# Claude Code one-liner:
claude mcp add --transport http kbaise https://kbaise.lovable.app/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.

Endpoint reference

GET /api/public/tools

Full directory. Filter with ?q=, ?cat=, ?tier=free, ?limit=

GET /api/public/tools/<slug>

One tool with full write-up, pricing and warnings.

GET /api/public/models

Latest provider docs and release notes, newest first.

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.