MCP server RoxyApi
Коммит 13 нояб. 2026 г.Provides a .NET SDK for accessing astrology, Vedic astrology, tarot, numerology, and human design data for AI agents and applications.
Также известен как RoxyAPI/sdk-dotnet
- Звёзды
- 2
- Инструменты
- —
- Загрузки, 30 дней
- —
- Последняя версия
- —
- Последний коммит
- 13 нояб. 2026 г.
- Лицензия
- MIT
Что такое RoxyApi MCP?
RoxyApi — это MCP server. Provides a .NET SDK for accessing astrology, Vedic astrology, tarot, numerology, and human design data for AI agents and applications.
Сводка сгенерирована из README проекта
О RoxyApi MCP server
This .NET SDK provides a unified way for developers to integrate spiritual and astrological data into applications like ASP.NET Core, Blazor, MAUI, and Unity. It serves as a single interface for accessing over 18 different domains, including Western astrology, Vedic astrology, tarot, numerology, and human design. By using a single API key, developers can retrieve highly specific data such as natal charts, daily horoscopes, kundli, and tarot spreads through a fully typed client.
The library is designed for ease of use, allowing for quick implementation with a single RoxyClient instance. It supports various environments including .NET 8, .NET Framework 4.6.1, and Mono. The SDK handles complex tasks like geocoding cities to obtain precise latitude, longitude, and IANA timezone strings, which are required for accurate astronomical calculations. All data is verified against NASA JPL Horizons to ensure precision for astrological transit forecasts and planetary positions.
Что вы можете с ним делать
- 1Generate Western natal chartsAn AI agent can calculate a user's Western natal chart using their birth date, time, and geocoded location data.
- 2Perform Vedic astrology analysisDevelopers can implement kundli generation and sidereal zodiac readings for matrimonial or astrological applications.
- 3Create tarot reading featuresAn application can provide tarot card meanings for specific life areas like love, career, or health.
- 4Build relationship compatibility toolsA dating app can use synastry to analyze the inter-aspect relationship between two different birth charts.
Взято из README проекта. Каждый вариант использования проверен на соответствие цитате из него.
Автоматические проверки
Запущено 15 нояб. 2026 г.Полный отчёт →Еще не проверено. Для сервера требуется оценка 80, отсутствие серьезных проблем и достаточно данных для нашей проверки. Как работают проверки · Что исправить, чтобы получить больше баллов
- Связанный и доступный исходный репозиторийroxyapi/sdk-dotnet is public and reachablegithub.com/roxyapi/sdk-dotnet ↗Пройдено
- Пакет указывает этот репозиторий как источникНе проверялось
- Происхождение сборки (аттестация Sigstore)Не проверялось
- Open source лицензия (OSI)MITspdx.org/licenses/MIT.html ↗Пройдено
- Коммит или релиз за последний годLast commit or release 2026-11-13github.com/roxyapi/sdk-dotnet ↗Пройдено
- OpenSSF ScorecardНе проверялось
- Имя пакета не похоже на популярный пакетНе проверялось
- Нет критических предупреждений в пакете или его зависимостяхНе проверялось
- Нет скрытых инструкций для модели0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersПройдено
- Деструктивные инструменты помеченыНе проверялось
- Удалённая конечная точка отвечает на рукопожатие MCPНе проверялось
README
Открыть на GitHubRoxyApi
The .NET SDK for astrology, Vedic astrology, numerology, tarot, and more.
One API key. Fully typed. Verified against NASA JPL Horizons.
The fastest way to add natal charts, daily horoscopes, synastry, Vedic kundli, tarot spreads, numerology, human design bodygraphs, and transit forecasts to ASP.NET Core, Blazor, MAUI, Unity, and AI agents. 18+ domains behind a single Roxy subscription, interpretations in 10+ languages, generated from the OpenAPI spec so new endpoints appear the day they ship.
Install
dotnet add package RoxyApi.Sdk
Or add it to your project file:
<PackageReference Include="RoxyApi.Sdk" Version="*" />
Targets netstandard2.0 and net8.0, so it runs on .NET 8 and later, .NET Framework 4.6.1 and later, Unity, and Mono.
Start with one call
Get real product value with a single typed call. No setup beyond your API key.
using RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
var horoscope = await roxy.Astrology.Horoscope["aries"].Daily.GetAsync();
Console.WriteLine($"{horoscope!.Overview}\n{horoscope.Love}\nLucky number: {horoscope.LuckyNumber}");
Then expand into charts, compatibility, numerology, tarot, and more.
Quick start
using RoxyApi;
using Microsoft.Kiota.Abstractions; // the Date and Time structs
// Retries 429, 500, 502, 503 and 504 by default. Optional settings, shown with their defaults:
// new RoxyClient(key, new RoxyRetryOptions { MaxRetries = 2, InitialDelay = TimeSpan.FromMilliseconds(500), MaxDelay = TimeSpan.FromSeconds(30) })
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
// Step 1: geocode the birth city once. Every chart endpoint takes these three values.
var place = await roxy.Location.Search.GetAsync(c => c.QueryParameters.Q = "London");
var city = place!.Cities![0];
// Step 2: a Western natal chart. city.Timezone is the IANA string from the lookup
// ("Europe/London"); the server resolves it to the DST-correct offset for the
// date of the chart.
var chart = await roxy.Astrology.NatalChart.PostAsync(new()
{
Date = new Date(1990, 1, 15),
Time = new Time(14, 30, 0),
Latitude = city.Latitude,
Longitude = city.Longitude,
Timezone = new() { String = city.Timezone },
});
// Step 3: the same birth as a Vedic kundli. Same inputs, sidereal zodiac.
var kundli = await roxy.VedicAstrology.BirthChart.PostAsync(new()
{
Date = new Date(1990, 1, 15),
Time = new Time(14, 30, 0),
Latitude = city.Latitude,
Longitude = city.Longitude,
Timezone = new() { String = city.Timezone },
});
new RoxyClient(apiKey) sets the base URL (https://roxyapi.com/api/v2) and injects the auth header and SDK identification header on every request. Every call returns the typed response and throws RoxyError on an error response (see Error handling).
Domains
Type roxy. to see every domain. Type roxy.Astrology. to see every endpoint in that domain.
| Accessor | What it covers |
|---|---|
roxy.Astrology |
Western astrology API for natal birth charts, daily, weekly, monthly, and yearly horoscopes with unique content per s... |
roxy.VedicAstrology |
Vedic astrology (Jyotish) and KP API for kundli generation with the sixteen Shodasavarga divisional charts (D1 to D60... |
roxy.Forecast |
Astrology forecast API that merges upcoming transit aspects, sign ingresses, retrograde stations, new and full moons,... |
roxy.HumanDesign |
Human Design API that generates the full bodygraph from a birth moment: type, strategy, inner authority, profile, def... |
roxy.ChineseAstrology |
Chinese zodiac and BaZi astrology API: Four Pillars charts, Chinese zodiac signs and the Chinese lunisolar calendar f... |
roxy.FengShui |
Compute classical feng shui from one API: Xuan Kong flying star natal charts for any of the nine periods and 24 mount... |
roxy.MesoamericanAstrology |
Calculate Mayan astrology day signs, the Tzolkin sacred round, the Haab year, the full Long Count and the Aztec tonal... |
roxy.Vastu |
Vastu Shastra API for directional home and plot analysis: entrance padas with the classical effect of each of the 32... |
roxy.Numerology |
Numerology API for life path numbers, complete numerology charts and compatibility, in both Pythagorean and Chaldean... |
roxy.Kabbalah |
Kabbalah API for gematria, the 72 names, the Tree of Life and the Hebrew birthday |
roxy.Tarot |
Tarot reading API with the complete 78-card Rider-Waite-Smith deck and card meanings for love, career, health, and sp... |
roxy.Biorhythm |
Biorhythm API for entertainment and reflection, with 10 model cycle types across 3 primary (physical, emotional, inte... |
roxy.Ayurveda |
Ayurveda API for dosha profiles, the dinacharya daily routine and the ritucharya seasonal regimen, with a verse cited... |
roxy.Iching |
I-Ching oracle API with all 64 hexagrams, 384 changing lines, 8 trigrams, and modern interpretations for love, career... |
roxy.Crystals |
Crystal healing API covering the most popular and widely-searched healing crystals and gemstones, from Amethyst and R... |
roxy.Dreams |
Dream interpretation API with a 2,200+ symbol dream dictionary and psychological meanings covering animals, objects,... |
roxy.AngelNumbers |
Angel numbers API with meanings for 111, 222, 333, 444, 555, 666, 777, 888, 999, 1111, and 75+ sequences covering eve... |
roxy.Location |
Timezone and location API with city search and geocoding across 5,180,000+ cities, towns and villages in 240+ countri... |
roxy.Usage |
Monitor your API usage, check rate limits, and track request consumption |
roxy.Reports |
Branded reports built from the API: a natal chart and more as a print-ready PDF, self-contained HTML or Markdown, whi... |
roxy.Languages |
List the response languages accepted by the lang query parameter on every i18n-aware endpoint |
Most-used endpoints
The highest-demand endpoints by domain, in the order you are most likely to ship them. Every example below reads the same birth through a different domain, and every coordinate comes from one location lookup at the top: one API key, one lookup, and eighteen domains that compose into a single product instead of eighteen separate ones. Full catalog in the API reference.
Location first: one lookup feeds every chart
Every chart, horoscope, panchang, dasha, dosha, synastry and compatibility endpoint needs Latitude, Longitude and Timezone. Never ask users to type coordinates. Look the city up once and reuse the result in every domain below. Request bodies are distinct generated types, so the values are captured once as locals and assigned into each body.
// One lookup feeds every chart below. timezone is the IANA name from the city
// record; the server resolves it to the DST-correct offset for the date of each chart.
var place = await roxy.Location.Search.GetAsync(c => c.QueryParameters.Q = "New York");
var city = place!.Cities![0];
var latitude = city.Latitude;
var longitude = city.Longitude;
var timezone = city.Timezone;
// The birth instant every chart below reads, beside the coordinates from the lookup.
var birthDate = new Date(1990, 1, 15);
var birthTime = new Time(14, 30, 0);
// A second person for the two-chart calls (synastry, Guna Milan, Human Design connection).
var london = await roxy.Location.Search.GetAsync(c => c.QueryParameters.Q = "London");
var partnerCity = london!.Cities![0];
var lat2 = partnerCity.Latitude;
var lon2 = partnerCity.Longitude;
var tz2 = partnerCity.Timezone;
var partnerDate = new Date(1992, 7, 22);
var partnerTime = new Time(9, 0, 0);
1. Western astrology API (natal chart, daily horoscope, synastry)
Natal chart products, daily horoscope features, dating and compatibility apps, and lunar-cycle wellness apps start here.
// Natal chart. The most requested Western call, run once at onboarding.
// The latitude, longitude and timezone come from the location lookup above.
var natal = await roxy.Astrology.NatalChart.PostAsync(new()
{
Date = birthDate, Time = birthTime,
Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// natal.Planets[n].Name, .Sign, .House, .Interpretation.Summary; natal.Ascendant.Sign; natal.Aspects
// Daily horoscope. The highest per-user call frequency in the catalog: daily content, streaks, push.
var horoscope = await roxy.Astrology.Horoscope["aries"].Daily.GetAsync();
// horoscope.Overview, horoscope.Love, horoscope.Career, horoscope.Column, horoscope.Events, horoscope.LuckyNumber
// Synastry. Full inter-aspect analysis between two charts, the relationship feature of dating apps.
// Both people come from the lookups above.
var synastry = await roxy.Astrology.Synastry.PostAsync(new()
{
Person1 = new() { Date = birthDate, Time = birthTime, Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone } },
Person2 = new() { Date = partnerDate, Time = partnerTime, Latitude = lat2, Longitude = lon2, Timezone = new() { String = tz2 } },
});
// synastry.CompatibilityScore, synastry.InterAspects, synastry.Analysis.Strengths
// Moon phase. A zero-setup GET for wellness, cycle-tracking and meditation apps.
var moon = await roxy.Astrology.MoonPhase.Current.GetAsync();
// moon.Phase, moon.Illumination, moon.Sign, moon.Meaning.Description
2. Vedic astrology API (kundli, panchang, dasha, Guna Milan, KP)
Kundli generators, matrimonial matching, muhurta and panchang apps, and KP practitioners. The same birth, read sidereally.
// Vedic kundli. The same birth read sidereally, from the same location lookup above.
var kundli = await roxy.VedicAstrology.BirthChart.PostAsync(new()
{
Date = birthDate, Time = birthTime,
Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// kundli.Meta.AdditionalData["Moon"] (every planet keyed by name: rashi, nakshatra, longitude), kundli.Houses, kundli.Yogas, kundli.Combustion
// Detailed panchang. Tithi, nakshatra, yoga, karana, rahu kaal and the muhurtas for a date at the place looked up above.
var panchang = await roxy.VedicAstrology.Panchang.Detailed.PostAsync(new()
{
Date = new Date(2026, 10, 1), Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// panchang.Tithi, panchang.Nakshatra, panchang.RahuKaal, panchang.AbhijitMuhurta
// Vimshottari dasha. The mahadasha, antardasha and pratyantardasha running right now.
var dasha = await roxy.VedicAstrology.Dasha.Current.PostAsync(new()
{
Date = birthDate, Time = birthTime,
Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// dasha.Mahadasha, dasha.Antardasha, dasha.RemainingInMahadasha
// Mangal Dosha. The most asked matrimonial check.
var dosha = await roxy.VedicAstrology.Dosha.Manglik.PostAsync(new()
{
Date = birthDate, Time = birthTime,
Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// dosha.Present; dosha.Severity and dosha.Remedies are set only when Present is true
// Guna Milan. The 36-point Ashtakoota score behind kundli matching, both people from the lookups above.
var milan = await roxy.VedicAstrology.Compatibility.PostAsync(new()
{
Person1 = new() { Date = birthDate, Time = birthTime, Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone } },
Person2 = new() { Date = partnerDate, Time = partnerTime, Latitude = lat2, Longitude = lon2, Timezone = new() { String = tz2 } },
});
// milan.Total, milan.Percentage, milan.IsCompatible, milan.Breakdown
// KP ruling planets. Horary answers at the moment of the question, for the place looked up above.
var kp = await roxy.VedicAstrology.Kp.RulingPlanets.PostAsync(new()
{
Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone },
});
// kp.DayLord, kp.MoonSublord, kp.RulingPlanets
3. Astrology forecast API (transit forecast, cross-domain timeline)
Forecast feeds, transit alerts and timing tools. One call returns a dated, significance-scored event list; the timeline variant merges Vedic dasha boundaries and biorhythm critical days into the same list, which no single-domain API can do.
// Transit forecast. Transit-to-natal aspects, sign ingresses and retrograde stations over a window.
// BirthData is the same birth: date, time, latitude, longitude and timezone from the lookup above.
var transits = await roxy.Forecast.Transits.PostAsync(new()
{
BirthData = new() { Date = birthDate, Time = birthTime, Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone } },
StartDate = new Date(2026, 10, 1), EndDate = new Date(2026, 10, 31),
});
// transits.Count, transits.Events[n].Date, .Type, .Body, .Target, .Aspect, .Significance
// Cross-domain timeline. The same window with Vedic dasha boundaries and biorhythm critical days merged in.
var timeline = await roxy.Forecast.Timeline.PostAsync(new()
{
BirthData = new() { Date = birthDate, Time = birthTime, Latitude = latitude, Longitude = longitude, Timezone = new() { String = timezone } },
StartDate = new Date(2026, 10, 1), EndDate = new Date(2026, 10, 31),
});
// timeline.Events[n].Domain (an enum: Western, Vedic, Biorhythm), .Description, .Significance
4. Human Design API (bodygraph, connection)
Self-discovery apps, coaching bots and compatibility products. The full bodygraph is one call, and the Design side is solved on the exact 88-degree solar arc rather than approximated as calendar days.
// Bodygraph. Type, strategy, authority, profile, definition, centers, channels and all 26 gates in one call.
// Human Design needs only the birth instant, so it takes the date, time and timezone from the lookup above.
var hd = await roxy.HumanDesign.Bodygraph.PostAsync(new()
{
Date = birthDate, Time = birthTime, Timezone = new() { String = timezone },
});
// hd.Type, hd.Strategy, hd.Authority, hd.Profile, hd.Definition, hd.IncarnationCross.Name, hd.Centers, hd.Channels, hd.Gates
// Connection. Two bodygraphs combined, each of the 36 channels classified by how the pair forms it.
var connection = await roxy.HumanDesign.Connection.PostAsync(new()
{
PersonA = new() { Date = birthDate, Time = birthTime, Timezone = new() { String = timezone } },
PersonB = new() { Date = partnerDate, Time = partnerTime, Timezone = new() { String = tz2 } },
});
// connection.TotalChannels, connection.Summary.Electromagnetic, connection.CombinedDefinition
5. Chinese zodiac API (BaZi four pillars, zodiac animal, almanac)
BaZi readings, zodiac content and Tong Shu date pages. The school splits that make two calculators disagree (DayBoundary, YearBoundary, HourClock) are typed request parameters with named defaults.
// BaZi Four Pillars. The anchor call of the domain, from the same birth instant as every chart above.
// Each response echoes the Conventions it was computed under, so a chart can be reproduced, not guessed.
var bazi = await roxy.ChineseAstrology.Bazi.Chart.PostAsync(new()
{
Date = birthDate, Time = birthTime, Timezone = new() { String = timezone },
});
// bazi.Pillars[n].Position ("year" | "month" | "day" | "hour"), .Stem.Element, .Branch.Animal, .TenGod.Name
// bazi.DayMaster.Element, bazi.ZodiacAnimal, bazi.FiveElements, bazi.Conventions
// Chinese zodiac animal. Defaults YearBoundary to the Lunar New Year, the folk rule people mean
// when they ask which animal they are. Pass LiChun for the classical BaZi boundary.
var animal = await roxy.ChineseAstrology.Zodiac.Sign.PostAsync(new() { Date = birthDate });
// animal.Animal.Name, animal.Animal.Element, animal.Element (the year stem element), animal.Interpretation
// Almanac day. The Tong Shu view of a date: day officer, mansion, clash animal, favours and avoids.
var almanac = await roxy.ChineseAstrology.Calendar.Day[new Date(2026, 10, 1)].GetAsync();
// almanac.DayPillar, almanac.DayOfficer, almanac.ClashAnimal, almanac.Favours, almanac.Avoids
6. Feng shui API (Kua number, flying star chart)
Kua numbers with the Eight Mansions map, Xuan Kong flying star charts for any of the nine periods and 24 mountains, annual and monthly star plates, and the annual afflictions.
// Kua number. One birth date and a gender give the personal directions everything else reads off.
// The enums live with their request bodies: using RoxyApi.FengShui.Kua; and using RoxyApi.FengShui.FlyingStars.Natal;
var kua = await roxy.FengShui.Kua.PostAsync(new() { Date = birthDate, Gender = KuaPostRequestBody_gender.Female });
// kua.Kua, kua.Group ("east" | "west"), kua.Trigram.English, kua.Sectors[n].Direction, .Nature, .Rank
// Flying star natal chart. Period plus facing gives the nine palaces with base, mountain and water stars.
// Send Facing (a mountain id like Bing or a compass label like S2) or FacingDegrees, not neither.
var stars = await roxy.FengShui.FlyingStars.Natal.PostAsync(new() { Period = 9, Facing = NatalPostRequestBody_facing.S2 });
// stars.Facing.Label, stars.Sitting.Label, stars.Structure.Name, stars.Palaces[n].Palace, .Base, .Mountain, .Water, .Reading
7. Mayan astrology API (Tzolkin day sign, full Maya chart)
Maya day signs, the Haab and Long Count, and the Aztec tonalpohualli, every value a function of the date under a typed Correlation convention echoed back in Conventions.
// Tzolkin day sign. The most asked Maya question, answered from a date alone.
var tzolkin = await roxy.MesoamericanAstrology.Mayan.Tzolkin.PostAsync(new() { Date = birthDate });
// tzolkin.DaySign, tzolkin.DaySignName, tzolkin.Number, tzolkin.Trecena, tzolkin.Reading
// Full Maya chart. Tzolkin, Haab, Long Count, Calendar Round, Lord of the Night, Year Bearer and the Cruz Maya.
var maya = await roxy.MesoamericanAstrology.Mayan.Chart.PostAsync(new() { Date = birthDate });
// maya.Tzolkin, maya.Haab, maya.LongCount, maya.CalendarRound, maya.YearBearer, maya.Cross, maya.Conventions.Correlation
8. Vastu Shastra API (entrance analysis, room compliance)
Home and plot analysis from typed geometry. Every verdict carries a Source object naming the text, chapter and verse it rests on, or a convention label where the texts are silent.
// Entrance analysis. Plot, facing and door in; the pada, its devata, the classical effect and the recommended padas out.
// The enums live with their request bodies: using RoxyApi.Vastu.Entrance; and using RoxyApi.Vastu.Rooms;
var entrance = await roxy.Vastu.Entrance.PostAsync(new()
{
Plot = new() { Width = 30, Depth = 40, Unit = EntrancePostRequestBody_plot_unit.Feet },
Facing = EntrancePostRequestBody_facing.North, DoorPosition = 0.4,
});
// entrance.Pada, entrance.Devata, entrance.Effect, entrance.Auspiciousness, entrance.RecommendedPadas, entrance.Source
// Room compliance. A verdict per room with the verse or the convention it rests on, and a scored composite.
var rooms = await roxy.Vastu.Rooms.PostAsync(new()
{
Plot = new() { Width = 30, Depth = 40, Unit = RoomsPostRequestBody_plot_unit.Feet },
Facing = RoomsPostRequestBody_facing.North,
Rooms =
[
new() { Type = RoomsPostRequestBody_rooms_type.Kitchen, Direction = RoomsPostRequestBody_rooms_direction.Southeast },
new() { Type = RoomsPostRequestBody_rooms_type.MasterBedroom, Direction = RoomsPostRequestBody_rooms_direction.Southwest },
new() { Type = RoomsPostRequestBody_rooms_type.Puja, Direction = RoomsPostRequestBody_rooms_direction.Northeast },
],
});
// rooms.Score, rooms.Rooms[n].Type, .Verdict, .IdealDirections, .Source
9. Numerology API (life path, full chart, personal year)
Works from the birth date and name alone, no coordinates, which makes it the easiest domain to integrate.
// Life Path. The most searched numerology number, from the birth date alone.
var lifePath = await roxy.Numerology.LifePath.PostAsync(new() { Year = 1990, Month = 1, Day = 15 });
// lifePath.Number, lifePath.Type (an enum: Single, Master), lifePath.Meaning
// Full numerology chart. All six core numbers plus karmic lessons, pinnacles and the personal year in one call.
var numerology = await roxy.Numerology.Chart.PostAsync(new() { FullName = "Jane Smith", Year = 1990, Month = 1, Day = 15 });
// numerology.CoreNumbers.LifePath, .Expression, .SoulUrge, numerology.AdditionalInsights.PersonalYear
// Personal Year. The annual theme, the January feature of every numerology app.
var personalYear = await roxy.Numerology.PersonalYear.PostAsync(new() { Month = 1, Day = 15, Year = 2026 });
// personalYear.PersonalYear, personalYear.Theme, personalYear.Advice
10. Kabbalah API (gematria, birth profile)
Gematria of a Latin name under a declared transliteration convention, the 72 names, the Tree of Life, and a Hebrew birthday computed from the same birth instant as every chart above.
// Gematria. A Latin name transliterated under a declared convention, ten ciphers, each with its tradition and source.
var gematria = await roxy.Kabbalah.Gematria.PostAsync(new() { Text = "Sarah" });
// gematria.Chosen.Hebrew, gematria.Values[n].Id, .Name, .Value, .Tradition; gematria.Matches, gematria.Conventions
// Birth profile. The Hebrew date and birthday, the three birth angels and the birth sephirah from the instant above.
var kabbalah = await roxy.Kabbalah.BirthProfile.PostAsync(new()
{
Date = birthDate, Time = birthTime, Timezone = new() { String = timezone },
});
// kabbalah.HebrewDate, kabbalah.HebrewBirthday, kabbalah.Angels, kabbalah.Sephirah
Вопросы о RoxyApi MCP
What programming languages and frameworks does the SDK support?
The SDK targets netstandard2.0 and net8.0, making it compatible with .NET 8 and later, .NET Framework 4.6.1 and later, Unity, and Mono.
How do I install the RoxyApi SDK?
You can install it via NuGet using the command dotnet add package RoxyApi.Sdk or by adding a PackageReference to your project file.
Does the SDK handle location and timezone data?
Yes, it includes a Location API for searching and geocoding cities to provide the latitude, longitude, and IANA timezone strings required for astrological charts.
