RoxyAPI

Menu

  1. Docs
  3. Build With Roxy
  5. AI Prompts

AI Prompts

Build with Roxy using AI coding tools. Whether you use Cursor, Claude Code, Windsurf, Copilot, or any AI assistant, these prompts give you working code in minutes.

Using AI agents instead? If your AI agent needs to call Roxy endpoints directly (not generate code), use MCP Setup instead. MCP lets agents auto-discover and call all Roxy tools without any prompting.

Step 1: Give your AI the Roxy knowledge base

Your AI tool needs to know what endpoints exist, what parameters they take, and what responses look like. Roxy publishes a complete knowledge base for this:

https://roxyapi.com/llms-full.txt

How to add it

Cursor: Go to Settings → Features → Docs → Add new doc → paste the URL. Now Cursor knows every Roxy endpoint when you @Docs reference it. You can also create a .cursor/rules/roxyapi.mdc file:

---
description: Rules for integrating RoxyAPI endpoints
globs: ["**/*.ts", "**/*.tsx", "**/*.js"]
---

When using RoxyAPI:
- Base URL: https://roxyapi.com/api/v2
- Auth: X-API-Key header (stored in env as ROXY_API_KEY)
- All endpoints return clean JSON, no wrapper objects
- Errors return { "error": "message" }
- Birth data uses ISO date "YYYY-MM-DD" and 24h time "HH:MM:SS"
- Reference @Docs for endpoint details

Claude Code: Add this to your project's CLAUDE.md:

## RoxyAPI Integration
- Base URL: https://roxyapi.com/api/v2
- Auth header: X-API-Key (env: ROXY_API_KEY)
- Full API reference: https://roxyapi.com/llms-full.txt
- Birth data format: { date: "YYYY-MM-DD", time: "HH:MM:SS", latitude, longitude, timezone }
- Numerology birth data: { year, month, day } (integers, no date string)
- Name-based endpoints use { fullName: "First Middle Last" }

Copilot / Windsurf / Other: Share https://roxyapi.com/llms-full.txt as context in your conversation or project docs.

Step 2: Use a prompt

Each prompt below is self-contained. Copy it, paste it into your AI tool, and it will generate working code.

Daily Tarot Card

Build a page that shows today's tarot card reading. Call the RoxyAPI tarot
daily endpoint: POST https://roxyapi.com/api/v2/tarot/daily with empty body {}.
API key is in env as ROXY_API_KEY, pass it as X-API-Key header.

Show the card image (response.card.imageUrl), card name, keywords array,
and the full meaning text. Handle reversed cards (response.card.reversed)
by showing a "Reversed" badge and noting the energy is internalized.
Show the dailyMessage as a summary at the top. Dark theme.

Zodiac Compatibility Checker

Build a form where two users enter birth details (date, time, city) and see
their zodiac compatibility. Use RoxyAPI compatibility-score endpoint:
POST https://roxyapi.com/api/v2/astrology/compatibility-score

Request body format for each person:
{ date: "YYYY-MM-DD", time: "HH:MM:SS", latitude: number, longitude: number, timezone: number }

Show the overall score (0-100) as a large number with a color indicator.
Show category breakdowns: romantic, emotional, intellectual, physical, spiritual.
Show strengths and challenges arrays as cards. Use the summary field as a headline.
API key from env ROXY_API_KEY, passed as X-API-Key header.

Numerology Life Path Calculator

Build a form where users enter their birth date and see their Life Path number.
Use RoxyAPI life-path endpoint: POST https://roxyapi.com/api/v2/numerology/life-path
Request body: { year: number, month: number, day: number }
API key from env ROXY_API_KEY, X-API-Key header.

Display the number prominently with the meaning.title as a subtitle.
Show meaning.description as the main text. Render meaning.strengths and
meaning.challenges as two-column cards. Show meaning.career, meaning.relationships,
and meaning.spirituality as expandable sections.

If hasKarmicDebt is true, show a highlighted section with the karmicDebtMeaning.
Show the calculation string so users can verify the math.

Birth Chart Reader

Build a birth chart input form (date, time, city with geocoding) and results page.
Use RoxyAPI natal chart endpoint: POST https://roxyapi.com/api/v2/astrology/natal-chart
Request body: { date: "YYYY-MM-DD", time: "HH:MM:SS", latitude: number, longitude: number, timezone: number }
API key from env ROXY_API_KEY, X-API-Key header.

Show the "big three" prominently: Sun sign, Moon sign, and Ascendant (rising sign).
Display all planets in a table showing planet name, zodiac sign, house number, and degree.
Show aspects as a list with the two planets, aspect type (conjunction, square, trine, etc),
and the orb in degrees. Group houses by life area.

Dream Journal

Build a dream journal where users describe a dream and look up symbols.
Use RoxyAPI dream symbol endpoint: GET https://roxyapi.com/api/v2/dreams/symbols/{symbolName}
API key from env ROXY_API_KEY, X-API-Key header.

Add a search input that calls GET /api/v2/dreams/symbols?search=query to find symbols.
Show each symbol's meaning, category, and related symbols.
Let users save dreams to local storage with date and symbols found.

Vedic Kundli Generator

Build a Vedic astrology birth chart (kundli) generator. Use RoxyAPI Vedic birth chart:
POST https://roxyapi.com/api/v2/vedic-astrology/birth-chart
Request body: { date: "YYYY-MM-DD", time: "HH:MM:SS", latitude: number, longitude: number, timezone: number }
API key from env ROXY_API_KEY, X-API-Key header.

Show the Lagna (Ascendant) prominently. Display planets with their rashi (sign),
nakshatra, and house placement. The Moon's nakshatra is the most important field.
Add a link to check doshas and compatibility using other Vedic endpoints.

Tips for better results

  • Include the exact request body format in your prompt. AI tools guess wrong when they don't know the schema.
  • Name specific response fields you want displayed. "Show the card.imageUrl" is better than "show the card image."
  • Mention error handling. Add "handle 401 (invalid key) and 429 (rate limited) errors with user-friendly messages."
  • Specify the framework if you have a preference: "Build this in Next.js" or "Use vanilla HTML + fetch."

Next steps

  • MCP Setup — connect AI agents directly to Roxy (no code generation needed)
  • Starter Apps — clone a production-ready app instead of generating from scratch
  • API Reference — browse all endpoints to find more things to build