Frequently Asked Questions

RoxyAPI offers monthly and yearly subscriptions, starting at $39 per month. Every plan includes all 18+ insight domains, every endpoint and Remote MCP. Annual Starter billing works out to $1.80 per domain per month; current prices and allowances are on /pricing.

Every RoxyAPI data request counts as one request, whether it returns a natal chart, a tarot reading or a numerology result. There are no premium-endpoint multipliers or per-domain add-ons. REST and Remote MCP use the same flat request pricing.

Compare the complete product you need to maintain: calculation verification, domain coverage, interpretations, localization, SDKs, UI and support. RoxyAPI includes these under one subscription across 18+ insight domains, with $1.80 per domain per month on annual Starter billing. Read /methodology and /policy/license, then test representative responses in /api-reference before deciding.

Refund eligibility and exceptions are defined in the published policy at /policy/refund. Cancelling stops future renewal charges, and API access continues through the paid period shown in your account. Evaluate the API reference and tools before subscribing.

RoxyAPI returns HTTP 429 when you reach the monthly allowance, with no automatic overage charge. You can wait for the next calendar-month reset or change to a plan with a larger allowance. The account dashboard shows usage and remaining requests.

You can change plans from the account dashboard while keeping the same API key. The new allowance applies after payment, and the unused value of the current plan converts into extra days on the new billing period. Review the checkout details before confirming a change.

The interactive API reference at /api-reference returns real production responses, so you can inspect requests, schemas and results before paying. Public calculators at /tools let you explore charts and readings without an account. MIT-licensed Templates at /templates show complete applications you can adapt.

Checkout offers the payment methods available for your selected currency, including cards and supported digital wallets. The available choices appear before you confirm the subscription. Contact us through /contact to arrange a cryptocurrency payment.

Enterprise is a quoted plan for high-volume applications and procurement requirements. It includes an account manager, negotiated contract terms and a 99.95% uptime SLA with service credits. Send your expected volume and integration requirements through /contact for a quote.

Any language that can make HTTPS requests and read JSON can use RoxyAPI. Official SDKs are available for TypeScript, Python, PHP, C#, and Go. The OpenAPI specification and examples at /api-reference document the same contract for other clients.

The API reference at /api-reference documents 261+ endpoints with request examples, response schemas and live testing. Guides at /docs cover integration, errors and domain-specific workflows. The same specification is available in OpenAPI format for client generation and validation.

RoxyAPI uses API keys for production integrations. Manage keys in your account, keep secret keys on your server and use publishable keys with origin restrictions for browser integrations. The authentication guide at /docs/authentication covers the setup for each context.

Each plan has a monthly request allowance and a per-minute limit for bursts, listed on /pricing. A rate-limited request returns HTTP 429; use the error code to distinguish a spent monthly allowance from a burst, and follow Retry-After when it is present. The error guide at /docs/errors explains the codes and retry behavior.

A serverless or edge function can call RoxyAPI over HTTPS and read the JSON response. Keep a secret key in the function environment and set timeouts and retries to suit your application. Test representative requests from your deployment region, since response time varies by endpoint, workload and network path.

RoxyAPI supports cross-origin browser requests with publishable keys restricted to your site origins. Roxy UI components and embeddable widgets can use those keys directly. Keep secret keys on your server; /docs/authentication explains the browser and server options.

Compare the endpoints, request parameters and response schemas in /api-reference with the features your application uses. Test your own representative inputs, including house systems, timezones and interpretation fields, before updating callers. A single subscription covers every RoxyAPI domain, so related features can use the same integration.

The location API searches cities and returns coordinates, province, country and an IANA timezone for a birth-data form. When a name has several matches, show the place details and let the user confirm the location. Pass the IANA timezone for a historical birth date so the chart uses the offset in force at that time.

RoxyAPI supplies charts and readings for astrology apps, daily horoscope feeds, compatibility features and AI reading assistants. The same subscription also supports Human Design tools, numerology calculators, tarot experiences and other insight products. SDKs, Roxy UI, embeddable widgets and MIT-licensed Templates provide ways to turn the data into a product.

RoxyAPI subscriptions support commercial applications, including paid readings, subscription apps and compatibility tools. Your application can keep its own branding and closed-source code under the commercial usage terms. Read /policy/license and /policy/terms for the conditions that apply to API data and redistribution.

RoxyAPI supplies the calculated charts, forecasts and readings that your model uses to answer a question. Connect your agent to a domain Remote MCP server, or call the REST API from your own application. You choose the model, prompts and memory, while MIT-licensed chatbot Templates at /templates provide working examples.

Horoscope and forecast endpoints provide dated readings and event data for newsletters, websites and editorial workflows. Your application controls publication, scheduling and presentation. Review the returned content and the commercial usage terms before publishing it under your brand.

RoxyAPI widgets provide charts and readings that you can embed in a site with an HTML block or hosted iframe. Roxy UI provides themeable components when you control the frontend, and the WordPress plugin offers another integration path. Browse /widgets and /ui to select the experience that fits your site.

RoxyAPI is the data layer for insight, belief and prediction products, with 18+ insight domains under one key. The catalog covers Astrology, Vedic, Forecast, Human Design, Chinese Astrology, Feng Shui, Mesoamerican, Vastu, Numerology, Kabbalah, Tarot, Biorhythm, Ayurveda, I-Ching, Crystals, Dreams, Angel Numbers, and Location. Western progressions, returns and astrocartography sit alongside Vedic KP, shadbala and dasha, with Remote MCP, SDKs, Roxy UI and Templates included.

Every RoxyAPI plan includes all 18+ insight domains and 261+ endpoints. A single secret key works across domains and their Remote MCP servers, with no separate product subscription. Browse /products for the complete catalog and domain capabilities.

Your subscription activates and an API key is created when payment completes. Follow the checkout confirmation or welcome email to retrieve the key, then keep it securely for your integration. The quick start guide at /docs/quickstart walks through the first request.

Test the live responses in /api-reference against the features and edge cases your application needs. Review /methodology for calculation verification, /transparency for published evidence and /pricing for request allowances. The versioned OpenAPI contract, SDKs, usage dashboard and support provide the integration surface for production use.

Roxy Ephemeris reads the NASA JPL DE440 ephemeris directly, so NASA JPL Horizons measures RoxyAPI work end to end. Gold-standard tests compare derived quantities against the authority named for each domain, while /methodology explains what each check covers. For the Sun, Moon, planets and Chiron, RoxyAPI returned 231 of 231 positions within 0.32 arcseconds (0.00009 degrees) of NASA JPL Horizons, at a median deviation of 0.05 arcseconds (0.00001 degrees). See roxyapi.github.io/astrology-api-benchmark for every domain, value and maximum.

Model Context Protocol lets an AI application discover tools and call them through a shared interface. RoxyAPI provides a Remote MCP server per domain over Streamable HTTP, exposing the domain calculations and readings as tools. Your application connects to the hosted server and uses its results within the conversation.

An MCP client that supports authenticated Streamable HTTP can connect to a RoxyAPI domain server. Supported configuration and transport options vary by client, so follow the client-specific guides at /docs/mcp. Applications can also use REST when their agent framework does not support Remote MCP.

The Docs MCP server searches RoxyAPI endpoint schemas and integration guides while a coding assistant works. AGENTS.md and llms.txt provide another way to read the documented contract and examples. Use the Docs server for integration work and the domain servers when a running application needs charts or readings.

A RoxyAPI domain tool call counts as one API request under the same subscription allowance as REST. Remote MCP carries no separate subscription or per-model token fee from RoxyAPI. Your chosen AI service bills its own model usage separately.

Several agents can connect to the domain servers their tasks require under one RoxyAPI subscription. An astrology agent can request a chart while a tarot or numerology agent requests a reading, and your application decides how to combine the results. Plan request limits apply to the combined usage.

Use a secret key for a RoxyAPI domain MCP connection and keep it in a trusted application or client configuration. The client receives that credential, so review its storage and access controls before connecting. Revoke exposed keys from your account and avoid putting secret keys in browser code or shared source files.

Your local application can connect to the same hosted RoxyAPI domain servers it will use in production. Test tool discovery, representative calls and error handling through the client you intend to ship. These are live API calls under your subscription, so account for development usage when choosing a plan.

Check /docs/mcp and /changelog for the supported integration behavior and published changes. Validate tool calls with your chosen client when upgrading its protocol implementation. API endpoint or version retirements are announced at least 90 days in advance under the Terms.

Western astrology includes natal charts, synastry, transits, progressions, returns and astrocartography. Vedic astrology includes kundli, divisional charts, Vimshottari dasha, panchang, KP, shadbala and compatibility. The product pages and /api-reference list the supported options and response fields for each technique.

The tarot API provides card draws, daily cards, yes-or-no readings and named spreads such as Celtic Cross, love and career. Custom spreads let you supply your own positions. Responses carry card meanings, upright or reversed orientation and reading context for a tarot app or agent.

The numerology API supports Pythagorean and Chaldean readings, complete charts, name analysis and compatibility. It includes Life Path, Expression, Soul Urge, Personality and personal date cycles, with interpretations and calculation steps. The product page documents the chosen conventions and handling of names in different scripts.

The Western astrology API provides daily, weekly, monthly and yearly horoscopes by zodiac sign. Responses combine planetary influences with editorial readings for the requested period. Your application can use them in horoscope pages, newsletters or scheduled notifications.

Western synastry compares birth charts, while composite charts and compatibility scores provide other relationship views. Vedic matching, Human Design connection charts and numerology compatibility offer separate systems under the same subscription. Choose the method your users expect and review its score definitions and interpretations in /api-reference.

Forecast endpoints combine Western transit events, Vedic dasha changes and biorhythm critical days into timelines, highlights and digests. Human Design returns bodygraphs with type, authority, profile, centers, channels and gates, alongside connection charts and transit overlays. Each domain has its own REST endpoints and Remote MCP server.

RoxyAPI returns structured JSON, with each endpoint documented by an OpenAPI schema. Charts and readings contain calculated data and the interpretation fields appropriate to that endpoint. Errors use HTTP status codes and a documented error body; /docs/errors explains the codes and fixes.

RoxyAPI provides individual calculation and reading endpoints, with no batch endpoint or push webhook. Make separate requests for separate subjects, and manage concurrency within your plan limits. For notifications, your application can poll forecast data, compare it with previous results and schedule the messages itself.

Supported Western endpoints let you choose the house system and lunar node type. Vedic endpoints let you choose an ayanamsa, including a custom value where documented. Options vary by endpoint, so use its request schema in /api-reference when matching a particular calculation convention.

RoxyAPI supports localized responses in 10+ languages: English, Turkish, German, Spanish, Hindi, Portuguese, French, Russian, Chinese (Simplified), Chinese (Traditional). Select the response language using the documented lang parameter. Coverage varies by domain and field, and a field without a translation returns English; product pages and /docs/guides/localization explain the available coverage.

The request and response schemas document the inputs and fields needed to build a chart or reading feature. SDKs, examples, Roxy UI and Templates help you use those responses in an application. Domain knowledge remains useful when choosing a technique and explaining its interpretation to your users.

Use /contact for questions about endpoint selection, setup or an integration issue. Include the feature you are building and a minimal request with credentials and personal data removed. The API reference, guides and Templates provide examples you can inspect before contacting support.

Email support is included on every RoxyAPI plan through /contact. Business and Enterprise plans include priority support, and Enterprise includes account management. The live API reference and guides remain available for self-service integration work.

Read the HTTP status, error code and documentation link returned with the response. Authentication and origin errors require a key or configuration fix, validation errors require corrected inputs, and rate limits require the appropriate reset or retry behavior. If a server error persists, send a minimal reproduction through /contact with credentials and personal data removed.

The public status page linked from /transparency reports measured availability and incidents. Professional plans have a 99.9% uptime SLA target, and Enterprise has a 99.95% target with service credits under its terms. Report an ongoing issue through /contact with the affected endpoint and error details.

Send the use case and the missing capability through /contact. Include the inputs you have and the result your application needs so we can assess the request. Shipped additions appear on /changelog and in the API reference.