AnyBio

Coding assistants

Build AnyBio-powered apps with Claude Code, Cursor, Lovable, or Bolt - start here if an AI tool writes your code.

If an AI tool writes your code, start here. AnyBio ships context files and paste-ready prompts so your assistant produces working integrations - correct CDN URLs, correct auth flow, correct widget markup - instead of guessing.

Three steps

Give your tool context

Download the context file for your tool and drop it in your project root:

  • Claude Code: ANYBIO.md - reference it from your CLAUDE.md
  • Cursor: .cursorrules
  • Lovable / Bolt: no file needed - the paste prompts below carry the context inline

This site also serves /llms.txt and /llms-full.txt, so any tool that reads docs URLs can pull the full reference directly.

Add your keys

Have your project key (proj_...) and API key ready from the AnyBio dashboard - your first sign-in creates an organization with a free sandbox. Keep the API key server-side - the guides below show the token-mode pattern for each platform.

Prompt in plain language

Paste a prompt from the AI prompt templates or write your own. With the context file in place, "add a mood check-in widget to my dashboard" produces correct <bio-provider> markup and a working token endpoint.

Per-tool guides

Each guide covers setup, working prompt patterns, and the failure modes we've seen that tool hit:

  • Claude Code - ANYBIO.md setup and terminal workflow
  • Cursor - .cursorrules setup and @docs usage
  • Lovable - Supabase Edge Function for token minting
  • Bolt - Next.js API route for token minting
  • AI prompt templates - copy-paste prompts for common builds

What your assistant should know

The short version of what the context files teach:

  • Widgets are standard web components from https://cdn.anybio.io/biosdk-web/v1/bioui.js, wrapped in one <bio-provider>.
  • Production auth is token mode: the backend calls POST /api/v1/sdk/token, the browser only holds a short-lived JWT.
  • Every widget needs a project-key and a user identity (xuser-id or xuser-token).
  • The full component and API reference lives on this site, indexed in /llms.txt.

On this page