AstroWay مقابل Astrology-API.io

Here's a full natal chart on AstroWay — copy-paste with a free key:

# cURL
curl -X POST https://api.astroway.info/v1/chart \
  -H "X-Api-Key: aw_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"date":"1990-07-14","time":"14:30","timezoneOffset":3,
       "latitude":50.45,"longitude":30.52}'

// Node.js (fetch)
const r = await fetch("https://api.astroway.info/v1/chart", {
  method: "POST",
  headers: { "X-Api-Key": process.env.ASTROWAY_API_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({ date: "1990-07-14", time: "14:30", timezoneOffset: 3,
                         latitude: 50.45, longitude: 30.52 }),
});
const { data } = await r.json();
console.log(data.planets[0]); // { name: "Sun", longitude: ... }

الطبقة الأولى 5 (مقارنة بـ $11). 50 ألف ائتمان (مقارنة بـ 1K). 12 نقاط نهاية HD (مقارنة بـ 1). 15 تقنية فريدة: تصحيح، توافق، antiscia، CCG، Gauquelin.

• دخول أرخص (5 مقابل $11)
• 50 ضعف ائتمانات أكثر لكل طبقة
• 12 مقابل 1 نقطة نهاية HD
• 15 تقنية فريدة مقابل 0
• OpenAPI 3.1 + MCP من الدرجة الأولى

A daily-horoscope app doing ~1,000 natal charts a month fits inside AstroWay’s free tier (10,000 credits ≈ 500 full charts) before you pay anything. Astrology-API.io’s entry tier is roughly $11 for 1K credits, so the same workload pushes you onto a paid plan quickly. AstroWay’s first paid tier starts at $5/mo.

Both speak JSON over HTTPS, so moving over is mostly remapping field names and swapping the base URL to api.astroway.info. The typed TypeScript and Python SDKs remove most of the manual mapping, and the OpenAPI 3.1 spec generates a client in any language.