# Yes No Tarot API

> Yes No Tarot API. Ask a specific question and receive a yes, no, or maybe answer based on a single tarot card draw. Upright cards indicate "Yes" with

- Capability page: https://roxyapi.com/apis/tarot-yes-no-api
- Full domain: https://roxyapi.com/products/tarot-api
- OpenAPI spec: https://roxyapi.com/api/v2/tarot/openapi.json
- Remote MCP server: https://roxyapi.com/mcp/tarot

## Overview

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.

## Endpoints

- `POST /api/v2/tarot/yes-no` Get yes/no answer to your question

## Example request

```bash
curl -X POST "https://roxyapi.com/api/v2/tarot/yes-no" \
  -H "X-API-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Should I accept the job offer?","seed":"optional-seed"}'
```

## Example response

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

## Remote MCP

Every endpoint is a callable tool on the Remote MCP server at https://roxyapi.com/mcp/tarot over Streamable HTTP. Tool name for `POST /tarot/yes-no`: `post_tarot_yes_no`. `tools/list` is free; `tools/call` bills the same as REST.

## 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.

## Full reference

Fetch the OpenAPI spec at https://roxyapi.com/api/v2/tarot/openapi.json. Master agent manifest at https://roxyapi.com/llms.txt.