Yes No Tarot API

Get yes/no answer to your question

POST/tarot/yes-no

Ask a specific question and receive a yes, no, or maybe answer based on a single tarot card draw. Upright cards indicate "Yes" with positive energy, reversed cards indicate "No" with caution, and certain inherently ambiguous cards (The Hanged Man, Wheel of Fortune, Temperance, Two of Swords, Four of Swords) return "Maybe" regardless of orientation since their energy signals pause, reflection, or shifting circumstances. Major Arcana cards give strong definitive answers, Minor Arcana cards give qualified nuanced answers. Returns the answer, strength level, drawn card details, and a contextual interpretation explaining why. Perfect for decision-making apps, quick guidance tools, fortune-telling chatbots, and interactive tarot experiences. Optionally provide a seed for reproducible answers.

Request

POST /api/v2/tarot/yes-no

Parameters

ParameterTypeDescription
langquerystring enumResponse language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default en.

Request body

FieldTypeDescription
questionstringYour specific yes/no question. Be clear and focused. Good: "Should I move to a new city?" Bad: "What should I do about my life?" The more specific the question, the more useful the tarot guidance.
seedstringOptional seed for reproducible results. Same seed + same question = same answer. Useful for testing, sharing readings, or ensuring consistency. Omit for random draws each time.

Example request

POST /tarot/yes-no
{
  "question": "Should I accept the job offer?",
  "seed": "optional-seed"
}

Response

Structured JSON with documented fields, verified against NASA JPL Horizons across 828 gold-standard tests. Not hallucinated text.

200 OK
{
  "answer": "Yes",
  "strength": "Strong",
  "card": {
    "id": "string",
    "name": "string",
    "arcana": "major",
    "reversed": true,
    "keywords": [
      "string"
    ],
    "imageUrl": "string"
  },
  "interpretation": "string"
}

Response fields

FieldTypeDescription
questionstringThe querent question that was asked, if one was provided.
answer*string enumTarot-derived answer. Yes = upright card supports a positive outcome. No = reversed card suggests obstacles. Maybe = inherently ambiguous card drawn (The Hanged Man, Wheel of Fortune, Temperance, Two of Swords, Four of Swords) signaling pause, reflection, or shifting circumstances.
strength*string enumConfidence level of the answer. Strong = Major Arcana card drawn (powerful, definitive cosmic energy). Qualified = Minor Arcana card drawn (nuanced, situational guidance).
card*object
card.id*stringUnique card identifier in kebab-case (e.g. the-fool, ace-of-cups).
card.name*stringDisplay name of the tarot card.
card.arcana*string enumWhether this card belongs to the Major Arcana (22 trump cards, major life themes) or Minor Arcana (56 suit cards, daily situations).
card.reversed*booleanTrue if the card was drawn reversed (upside down). Reversed cards carry modified or blocked energy compared to upright position.
card.keywords*array of stringKey themes and concepts associated with this card in its current orientation (upright or reversed).
card.imageUrl*stringURL to the tarot card artwork image.
interpretation*stringContextual narrative explaining why this card answers the question with this result. Connects card meaning, orientation, and arcana strength into actionable guidance.

Supported options

lang

entrdeeshiptfrru

Call it in your language in seconds.

Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.

TypeScript
import { createRoxy } from '@roxyapi/sdk'

const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.tarot.castYesNo({ body: { question: 'Should I accept the job offer?', seed: 'optional-seed' } })
Install: npm install @roxyapi/sdk

Prefer to try before you write code? Run this Tarot endpoint live in the API playground and inspect a real production response.

Remote MCP for AI agents

Every Tarot endpoint is a callable tool on the Remote MCP server over Streamable HTTP. No local setup, no Docker. Claude, ChatGPT, Cursor, and any MCP client auto-discover the tools and ground their answers in verified data.

Claude Code / Cursor
claude mcp add --transport http \
  roxy-tarot https://roxyapi.com/mcp/tarot \
  --header "X-API-Key: YOUR_KEY"

Tool name for POST /tarot/yes-no: post_tarot_yes_no. Full MCP setup guide

What you can build

Build tarot reading apps with authentic Rider-Waite-Smith interpretations: upright and reversed meanings for all 78 cards with domain-specific guidance for love, career, health, and spiritual growth

Add daily tarot features to wellness and self-discovery platforms: date-based seeded draws ensure consistent personalized cards each day with shareable results

Build AI tarot chatbots with MCP: your OpenAI, Claude, or Gemini agent auto-discovers tarot endpoints and delivers conversational readings with zero integration code

Power career and life coaching platforms with Celtic Cross (10-card), SWOT career spreads, and yes/no oracle readings for decision-making and guidance features

Create relationship and dating app features with love spreads analyzing emotional dynamics, compatibility, challenges, and partnership potential

Ship fortune-telling and divination platforms combining tarot with astrology, numerology, dreams, and I-Ching for comprehensive spiritual guidance under one API key

Drop-in UI components

Render Yes No Tarot API responses without building charts yourself. These open source, framework-agnostic web components take the typed response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.

<roxy-tarot-spread>
See them live on Roxy UI

Related capabilities

Yes No Tarot API FAQ

What does the Yes No Tarot API return?

Ask a specific question and receive a yes, no, or maybe answer based on a single tarot card draw. Every response is structured JSON with documented fields, not free text, so you map it straight into your product.

How do I authenticate with the Yes No Tarot API?

Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.

Does the Yes No Tarot API support multiple languages?

Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.

Is the Yes No Tarot API available over Remote MCP for AI agents?

Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/tarot over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.

How is the Yes No Tarot API billed?

Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the Yes No Tarot API is included at no extra cost.

What lang values does the Yes No Tarot API accept?

The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.

Start using Yes No Tarot API today.

Launch a tarot reading app with 78-card authenticity. In days.

All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.

Plans from $39/mo, starting at $2.70 per domain on annual billing. No credit card required for testing.

View Pricing & Get API Key